How to Send a Website Screenshot to Microsoft Teams with Power Automate

To send a website screenshot to Microsoft Teams with Power Automate, use a desktop flow to capture the page as an image file, put that file somewhere your cloud flow can access (such as SharePoint or OneDrive), and use the Microsoft Teams connector’s Post a message in a chat or channel action to post a message with a link to the image. A local file path on the desktop machine is not, by itself, a cloud-flow input. The documented Teams message action does not establish that it embeds an image inline in every destination, so treat a link to the stored screenshot as the dependable outcome unless you have verified a supported attachment method for your exact scenario. [Microsoft screenshot action reference; Teams connector guide; Teams messaging APIs]

How the workflow fits together

Capture on the desktop: Power Automate for desktop launches or attaches to a browser, navigates to the page, waits for it, then saves a full-page or element screenshot.
Hand off the image: Copy or save the image into cloud-accessible storage. SharePoint is one documented option; an appropriate OneDrive location can also be used where it is available in your environment.
Post to Teams: A cloud flow uses the Teams connector to post a message containing the file link or reference.

This division matters: browser capture runs in the desktop flow, while the Teams connector action runs in a cloud flow. Microsoft describes Teams file attachments as references to files in accessible storage, such as SharePoint; the reference points to the stored content. [Microsoft Graph Teams messaging overview]

Prerequisites and decisions

Power Automate for desktop and a machine that can run the desktop flow.
A supported browser installed and available to the flow. Microsoft’s browser automation documentation describes Edge, Chrome, Firefox, Internet Explorer, and the Automation browser; check the current documentation and your environment before choosing a browser. [Automate webpages]
A cloud flow with a Microsoft Teams connection, plus access to the destination chat or channel.
A cloud-accessible place to store the screenshot and permissions that let the intended recipients open it.

Choose the capture and delivery behavior before building:

Choice	Use it when	Trade-off
Entire webpage	The overall page and its context matter.	May produce a tall, large image; the page must render the content you need.
Specific element	You need a chart, status panel, or other focused region.	Depends on selecting a current webpage element; a missing selector or changed page structure can break capture.
Save to file	A later cloud step needs a durable handoff.	Requires a writable path and a separate move or upload to cloud storage.
Save to clipboard	The next local operation consumes the image immediately.	Less explicit as a cloud handoff and clipboard saving can fail; prefer a file for this workflow.
Message with link	Recipients need to open the saved screenshot.	They need permission to access the file. This is the documented file-reference pattern.
Inline/native image	The image must render directly in the conversation.	The standard posting guide reviewed does not document a universal image upload field. Verify the exact connector or Graph method and required permissions before depending on it.
Flow bot or connected user	Choose based on the identity that should appear as sender and your organization’s governance.	Available sender choices depend on the action and destination; review the current connector guide.

Step 1: Build the desktop capture flow

Create a desktop flow and add the browser launch action for a new browser instance, or attach using a supported method. Browser actions need a browser instance. Most webpage actions also need web UI elements captured from the loaded page.
Navigate to the target URL. Add the appropriate wait so the content you want is visible before capture. If content is rendered asynchronously, wait for the relevant state rather than relying only on navigation starting.
Add Take screenshot of web page. Select Entire web page or Specific element. For the latter, choose the webpage UI element to capture.
Choose File as the save mode and a supported format such as PNG or JPG. The action reference lists BMP, EMF, EXIF, GIF, JPG, PNG, TIFF, and WMF. Set a full output path, for example C:\\Users\\Public\\Documents\\site-capture.png, and ensure the flow account can write there.
Run the flow and confirm the resulting image is legible and contains the intended page or element.

Use web UI elements for page content. Power Automate distinguishes those from desktop UI elements such as browser tabs and address bars; the two types are not interchangeable in browser actions. [Automate using UI elements]

The desktop action can save to a file or clipboard. A file makes a clearer handoff because it can be copied or uploaded to storage for the cloud flow. The documented action reference lists failure cases for a missing CSS selector, saving the file, saving to the clipboard, and capturing the screenshot. [Browser automation actions reference]

Step 2: Move the screenshot into cloud-accessible storage

A path such as C:\\Users\\Public\\Documents\\site-capture.png identifies a file on the desktop machine; it does not automatically make that file available to a cloud flow. Add a handoff that places the image in a location accessible to the cloud workflow. For example, use an appropriate SharePoint or OneDrive destination, or another supported storage handoff already available in your environment.

Choose the target library or folder and decide who must be able to open the file.
Copy or upload the screenshot there after capture. Keep the output name predictable if the flow processes repeated captures; use a unique name or a deliberate overwrite policy to avoid collisions.
Make the cloud flow receive the file-created event or otherwise obtain the file’s link/reference from the storage step.
Check access using the identity and audience that will receive the Teams message. A link is only useful if its sharing permissions match your intended audience.

Microsoft’s Teams guide shows a SharePoint file-created trigger as a cloud-flow pattern, while Graph describes file attachments as references to files in accessible storage. [Send a message in Teams using Power Automate; Teams messaging APIs]

Step 3: Post the screenshot link in Teams

Create a cloud flow triggered by the storage handoff, such as the relevant file-created event, or by another supported trigger in your setup.
Add Microsoft Teams Post a message in a chat or channel.
Choose the sender mode supported for your destination (for example, Flow bot or the connected user), then select the team/channel or chat.
Write a useful message with context and insert the file link/reference from the previous storage step. Include the page URL and capture time if those values are available in your flow.
Save and run an end-to-end check. Open the posted link as a recipient to confirm the file is reachable.

The connector guide documents message posting with dynamic content and sender/destination choices. It also lists constraints: private-channel posting is unsupported for this action; user mentions have limitations; the action cannot mark a message urgent or important. The destination dropdown defaults to recent group chats and shows 50 by default; if the intended chat is absent, the guide describes creating a chat and passing its conversation ID. Consult the current connector documentation for destination-specific restrictions. [Teams connector guide]

Link versus inline image

There are two different requirements that are often called “send the screenshot”:

Clickable screenshot: Store the image in accessible cloud storage and post its link/reference. This matches the documented file-reference model.
Image rendered inline in the message: The connector guide reviewed does not establish that the ordinary message action uploads and embeds an image in every chat and channel. If inline display is required, verify a supported connector or Microsoft Graph implementation for the specific destination, storage model, permissions, and message format before treating it as guaranteed.

Do not assume that inserting a local file path into message text uploads the image. The path must be made accessible and represented in a form Teams recipients can open.

Edge cases and reliability

Dynamic pages: A page may navigate before its chart or other content is ready. Wait for the relevant web UI element or an appropriate page state before capturing.
Long pages: Entire-page images can be tall and may be awkward to view in Teams. Consider capturing a focused element when the audience needs a particular panel.
Changing layouts: A selected element or CSS selector can stop matching after a site update. Re-capture or update the UI element and handle a missing-element failure explicitly.
Repeated runs: Avoid two runs overwriting a file before the cloud flow processes it. Use unique filenames or coordinate the storage trigger and cleanup policy.
Access changes: A working link can later fail if permissions or the file’s location change. Test with the audience identity and keep the file in a managed location.
Desktop session state: Some physical-interaction web actions require the browser tab to be focused and the browser not minimized. If the flow uses such actions, keep an interactive session available. [Automate webpages]
WebDriver mode: WebDriver-based automation can attach only to browser instances launched by the flow, not manually opened instances. Match the driver to the browser version and place it in the documented Power Automate Desktop WebDrivers directory. [Browser automation actions reference]

Troubleshooting

Symptom	Likely cause	Fix
Screenshot action cannot find the element	The selector/UI element is missing, stale, or refers to the wrong UI element type.	Confirm the page loaded, capture the current web UI element again, and use a webpage element rather than browser chrome. Add a wait for dynamic content.
Image is blank or missing content	Capture ran before the page or target content finished loading.	Wait for the required element or content state before taking the screenshot; inspect the page in the flow’s browser session.
File-save error	The output path is invalid, unavailable, or not writable by the flow account.	Use a valid full path, create the parent folder, check access, and verify available storage.
Clipboard-save error	The clipboard operation failed or the environment cannot provide the expected clipboard state.	Use file output for the cloud handoff, or diagnose the local clipboard/session configuration.
Screenshot-capture error	The browser instance or capture target is invalid, or the page is not ready.	Verify the browser was launched/attached by the flow, the selected target exists, and capture occurs after loading. Review the action error details.
Cloud flow cannot find the local image	The desktop path has not been handed to cloud-accessible storage.	Add an upload/copy step to SharePoint, OneDrive, or another supported destination and pass the resulting file reference to the cloud flow.
Teams recipient cannot open the link	The file permissions do not include the recipient, or the link points to the wrong item.	Check the stored file and its sharing scope with the intended recipient identity; generate/use the correct accessible reference.
Destination chat is missing	The dropdown lists recent group chats only by default.	Use the documented conversation-ID approach where appropriate, or select a supported destination. Check current connector restrictions.
Private channel cannot be selected or posting fails	The standard action lists private-channel posting as unsupported.	Use a supported destination or investigate a separately documented implementation that meets your organization’s permissions and requirements.

Microsoft’s screenshot action reference specifically lists selector-not-found, file-save, clipboard-save, and screenshot-capture errors. [Action reference]

Performance, reliability, and cost notes

Performance: Capture time depends on page loading and the size of the page or selected element; a full-page capture and its upload may move more data than a focused crop. Wait only for the content required by the screenshot, while allowing enough time for dynamic rendering.
Reliability: Treat capture, upload, and Teams posting as separate steps. Record or surface failures at each handoff, use stable filenames or unique run identifiers, and check that the file exists before posting its link.
Permissions: The flow’s storage and Teams connections determine what it can write and where it can post. The recipients’ file access is a separate check from the flow’s successful post.
Cost: The research sources do not specify Power Automate licensing costs, storage quotas, or tenant-specific charges. Check your organization’s Microsoft licensing and storage terms rather than assuming this workflow is included at no additional cost.

Or skip the browser setup

If you only need to capture a website and deliver the resulting image through your own integration, ScreenshotNeo is a website screenshot API and MCP server. One GET request returns a PNG, JPEG, WebP, or PDF. You still need to place the result in storage that your Teams flow can access and post the resulting link/reference.

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,
)
r.raise_for_status()
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}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', image));

See the ScreenshotNeo API documentation for request options. Cookie banners, newsletter popups, and chat widgets are removed before capture; each cleanup step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers report the page verdict and billing status. An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots.

FAQ

Can Power Automate capture only part of a webpage?

Yes. The screenshot action supports capturing a specific webpage element as well as the entire webpage. The selected element must exist when the action runs.

Can I use JPG instead of PNG?

Yes. JPG and PNG are among the formats listed for the desktop screenshot action; choose the format supported by your later storage and viewing workflow.

Will the image appear inline in every Teams chat?

The reviewed standard message action documentation does not promise that. A message containing a link to an accessible stored image is the supported pattern described here; verify a specific attachment method if inline rendering is mandatory.

Can the message be posted as a user?

The connector offers sender choices such as Flow bot and the connected user in documented scenarios. The available choice depends on destination and connector behavior; check the current guide.

Does the Teams action support private channels?

The connector guide lists private-channel posting as unsupported for this action. Use a supported destination or another currently documented method that meets your requirements.