How to Send a Website Screenshot to Microsoft Teams with Make

To send a website screenshot to Microsoft Teams with Make, create a scenario with HTML/CSS to Image → Create a Screenshot of a URL, then connect it to Microsoft Teams → Send a Message. Make documents both actions. The important detail is the screenshot module’s output: inspect whether it provides image data, a downloadable URL, or another reference, then map it to a field the current Teams module accepts. A URL posted as message text may show only as a link, not as an image attachment.

Make describes scenarios as workflows made from modules, with mapping used to pass data from one module to the next. Its integration catalog lists the screenshot action for a website URL and a Teams message action for a channel or chat. The catalog does not define a universal image-attachment procedure, so verify the fields and rendered result in your own scenario and Teams tenant. Make integration listing; Make mapping documentation.

Build the Make scenario

1. Create a scenario. In Make, start a new scenario and add the HTML/CSS to Image app.
2. Choose the URL screenshot action. Select Create a Screenshot of a URL. Enter the webpage URL and configure any capture settings shown in the current module.
3. Add Microsoft Teams. Add Send a Message, connect the Microsoft account, and select the intended team and channel or chat.
4. Run a test capture. Use a page you are allowed to capture. Run the scenario once and open the screenshot module’s output bundle.
5. Inspect the output shape. Determine whether the module returns file data, a downloadable URL, or another value. Note the exact output field and whether it expires or requires authentication, if those details are provided.
6. Map the output. Map it into a field supported by the live Teams module. If you want an image attachment, confirm the path really uploads or attaches the image. If the module only accepts message text, a URL in the message is a link, not necessarily an attachment.
7. Test the received message. Run the scenario again and inspect the result in the intended Teams tenant and client. Confirm that the message went to the right destination and that the image is visible in the expected way.
8. Schedule or activate the scenario. Do this only after the test output and destination are correct.

Module field names and available options can change. Follow the fields currently displayed in your Make account rather than assuming a fixed mapping from a screenshot or older tutorial.

Link versus image attachment

There are two different outcomes people mean by “send a screenshot.” A message containing a screenshot URL gives recipients a link to open. An image attachment uploads image bytes or a file to Teams so the image appears as an attachment or preview. Do not treat these as interchangeable.

Screenshot output	What to check	Likely next step
File or binary data	Does the Teams action expose a file or attachment input, and does it accept the mapped data?	Map the file using the supported field and verify the received message.
Downloadable URL	Can the Teams action accept a URL as an attachment, or only as message text? Is the URL accessible to the intended recipients?	Use a supported upload or attachment route if an inline image is required; otherwise send the link and label it clearly.
File reference or other object	What does the live module expect, and does the reference remain accessible long enough for the next step?	Inspect the bundle and module help, then map only the accepted value.

Make’s documentation for its HTTP app describes support for mapping a file from an earlier module into a multipart/form-data request. It also says HTTP URLs must begin with HTTPS, self-signed certificates are rejected, and a setting can stop a scenario when the response is 4xx or 5xx. These are useful building blocks if your chosen route needs an HTTP transfer, but they do not establish a universal sequence for uploading an image to Teams. Check the current Teams and upload API requirements before building that route. Make HTTP app documentation.

Alternative capture route: GetScreenshot

Make also documents a GetScreenshot app with Take Screenshot and Take Element Screenshot actions. Its Make documentation says an active account and API key are required. Make labels that app documentation AI-generated and warns it may contain mistakes, so verify the integration and its output with the vendor before relying on it. This can be useful when you need element capture, but it adds a separate account and key to configure. Make GetScreenshot listing.

Common problems and fixes

Problem	Likely cause	What to do
The Teams message contains a URL but no visible image	The screenshot URL was mapped into message text. A link is not the same as an uploaded attachment.	Check whether the current Teams module supports an attachment or file input. If it does, follow its upload requirements. Otherwise describe the link as a link.
The message sends, but the screenshot cannot be opened	The returned link may require authentication, be inaccessible to recipients, or no longer be available.	Check access from a recipient’s account and inspect the provider’s link behavior and lifetime. Use an upload flow supported by the destination when needed.
The screenshot step succeeds but Teams receives an empty value	The wrong output field or an object that the next module cannot consume may have been mapped.	Run the capture step, inspect its output bundle, and map the actual file or URL field supported by Teams.
The scenario fails during an HTTP transfer	The URL may not use HTTPS, the certificate may be unverified, or the request may not match the receiving endpoint’s expected format.	Use an HTTPS endpoint with a valid certificate and confirm the required request format and mapped file data. Configure Make’s error behavior deliberately.
The capture is blank or incomplete	The page may need time to render, may block automated access, or the supplied address may not show the expected content without a session.	Check the page URL and the capture module’s available wait or rendering settings. Test with an authorized page and inspect the capture output before troubleshooting Teams.
The message goes to the wrong place	The Teams destination selection may point to a different team, channel, or chat than intended.	Recheck the selected destination in the Teams module and verify it with a test message.

Reliability, performance, and cost considerations

• Test each handoff. Keep capture and delivery failures distinct: inspect the screenshot output first, then confirm Teams accepts the mapped value and the recipient can access it.
• Account for page variability. Dynamic content, access controls, consent prompts, and slow rendering can change what a URL capture returns. Use the capture module settings available in your scenario and validate representative pages.
• Keep credentials and access in mind. If a capture URL or file needs authentication, confirm that the next module and the recipients can access it. Do not place sensitive credentials in a message.
• Handle errors intentionally. Make’s HTTP app can be configured to stop a scenario on 4xx or 5xx responses. Choose error handling that makes failed transfers visible instead of silently treating them as successful delivery.
• Check current plan and module limits. The cited Make documentation does not establish current pricing, quotas, latency, or service-level guarantees for this specific scenario. Review the live product details for your account before estimating ongoing cost or throughput.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. Make can use its API as a capture step when you prefer a single request that returns a screenshot; you still need to map or upload the result through the Teams module that your scenario supports. Its captures accept cookie and consent banners like a visitor and remove more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents use screenshot tools. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. See the ScreenshotNeo website and API documentation.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

These examples save or retrieve the screenshot response; connect that output to a Teams upload or attachment route supported by your Make scenario if you need an inline image. See ScreenshotNeo’s API documentation for request options and response details.

Create a free ScreenshotNeo account for 1,000 screenshots a month with no card.

FAQ

Can Make automatically send a webpage screenshot to a Teams channel?

Make lists a URL screenshot action and a Teams message action. Configure the destination and verify how the screenshot output is accepted and rendered in your tenant.

Can I send a screenshot to a Teams chat instead?

The Make catalog describes Send a Message as posting to a channel or chat. Choose the destination exposed by the current module.

Can I trigger the capture from a Teams message?

Make lists a Teams Watch Messages trigger for a channel or chat. Its catalog says Watch New Replies is not available for Personal accounts. That trigger is optional and not needed for a one-way capture-to-message scenario. Microsoft Teams integration listing.

Will a screenshot link always appear inline in Teams?

No. A link in message text may remain a link. Confirm the current module’s attachment behavior and inspect the actual message.