Power Automate integration
Take website screenshots inside your Power Automate flows.
A certified connector with four actions: capture a page, capture it from a real location, render your own HTML, or capture and have AI read it. Then send the image to Teams, OneDrive, or anything else in your tenant.
- Take screenshots in a flow and send the images to Teams, OneDrive, and other services.
- Render an email or another connector's data as an image with the custom HTML action.
- Capture and have AI analyse the image in the same action.
- Capture content as it really appears in other countries, cities, and US states.
25 free screenshots / month · no credit card · no phone number
-
Trigger Recurrence, every weekday Schedule
-
Action Take a screenshot of a web page PagePixels
-
Action Create file OneDrive
-
Action Post a message Teams
How to take a screenshot in Power Automate in four steps
Nothing to install in the tenant beyond the connector itself. If you have built a flow before, skim this.
-
Create a free account
Sign up for PagePixels first, because the connector authenticates against an account. Every feature is on the free plan.
25 screenshots / mo -
Add the connector
In the flow designer, search for PagePixels Screenshots, add it as a step, and connect it when prompted.
search: PagePixels -
Choose the action
Take a screenshot of a web page, take one from a real geolocation, take one of custom HTML, or take one and analyze the image with AI.
one of four actions -
Use the file downstream
The action returns the capture. Post it to Teams, create it in OneDrive, attach it to an approval, or write it against a record.
output → next step
Our walkthrough is the Power Automate guide. Microsoft publishes the connector reference, action by action, at learn.microsoft.com, which is the place to check exactly which fields each action takes.
Four published actions, and only one of them starts with a plain URL.
These are the action names as Microsoft documents them, so what you search for in the designer matches what you read here.
-
Capture a web page
01The straightforward case: give it a URL and the options you want, and it returns the capture for the rest of the flow.
-
Take a screenshot of a web page
-
-
Capture from a real location
02Render the page as it actually appears in another country, city, or US state, rather than from a datacentre in the wrong hemisphere.
-
Take a real geolocation screenshot of a web page
-
-
Capture your own HTML
03Turn an email body or data from another connector into an image, for the things worth keeping that were never a web page.
-
Take a screenshot of custom HTML
-
-
Capture and analyse with AI
04Take the screenshot and get a written answer about it back with the image, so a later step can act on the content.
-
Take a screenshot of a web page and analyze the image with AI
-
Straight into the place your organisation already works.
The connector returns the capture as a file, so the next step is whatever you would normally do with one: post it to Teams, create it in OneDrive, attach it to an approval, or write it against a record.
- The image png · jpeg · webp · pdf
- The capture itself, full page or one selector, ready for Create file, an attachment, or a Teams post.
- A permanent link embed url
- Always resolves to the latest capture of that config, with no API key in the URL, so it is safe to paste into a channel or a doc.
- The archive copy kept here
- Every capture is filed in the archive and listable through the API, whatever the flow does with its own copy.
- The AI answer written answer
- From the AI action: the analysis text travels with the image so a condition can branch on it.
- Rendered HTML html
- Optionally the fully rendered markup, for a step that parses rather than looks.
Worth knowing before you build: scheduling, change detection, and delivery to Slack, Dropbox, or a webhook are built in here, so captures can recur without a flow running. Use Power Automate when the capture belongs inside a Microsoft 365 process, or has to reach a connector we do not integrate with directly.
The internal pages you want are all behind a login.
That is the normal case in a Microsoft 365 shop: a supplier portal, an internal dashboard, a partner site that wants credentials. A renderer that only accepts a URL returns the sign-in page, on schedule, forever.
Multi-step capture is what gets past it: log in, click links, fill out forms, run custom scripts, and only then capture. It is part of the capture engine on every plan, so the step list you build in the web app or the API is the same engine the connector calls.
Captures can also run from a Real Location in 150+ countries, states, and cities, which is the connector's own second action.
-
Open the login page url
-
Fill email and password text_field ×2
-
Click submit click
-
Wait for the dashboard wait_for_selector
-
Capture the page png · full page
-
Return the file to the flow connector output
Four flows worth ten minutes
Each is a trigger, one connector action, and a destination already in your tenant.
-
Recurrence → capture → Teams
The morning page, in the channel
Capture the dashboard or supplier portal every weekday and post it into the team channel, so the first person online does not have to go looking.
weekdays 08:00 · Teams -
Outlook → custom HTML → OneDrive
Emails filed as pictures
Render an incoming invoice or report email as an image and file it in OneDrive, so the record is what arrived rather than a thread to reconstruct.
on new email · OneDrive -
Approval → capture → attachment
Evidence inside the approval
Capture the page under review and attach it to the approval request, so whoever signs off is looking at the same thing you were.
on request · approval step -
Real geolocation → Teams
Check what other markets see
Capture a campaign or pricing page from the countries you sell in and post the set for review, without a VPN or a colleague in that office.
weekly · 4 locations
The connector is not a paid tier.
This list is the same on the free plan and the largest one, and the same through the connector, the API, and the web app.
Capture
5 INCLUDED- Multi-step capture Log in, click, fill forms, and wait for elements before the shutter fires.
- Scheduled screenshots Recurring captures from every five minutes to once a year.
- Real Locations Capture through a proxy network in 150+ countries, US states, and cities.
- Ad, tracker, and banner removal Strip cookie consent walls, ads, and third-party scripts before capture.
- CSS and JS injection Restyle or manipulate the page before the capture is taken.
Understand
4 INCLUDED- AI analysis Ask a question of any capture and get a written answer back with the image.
- Custom HTML screenshots Render email, private spreadsheet rows, or API payloads into an image.
- HTML extraction Pull fully rendered HTML from JavaScript-built pages, whole page or one selector.
- Website domain research Extract structured fields across a list of domains, as JSON or CSV.
Watch
3 INCLUDED- Change notifications Watch a selector and get a webhook, Slack message, or Zap when it moves.
- Archived history Every capture is kept and listable through the API, with dated thumbnails.
- CDN embed URLs A permanent link that always shows the latest capture, no API key exposed.
Deliver
3 INCLUDED- Every integration Zapier, Make, n8n, Power Automate, Slack, Dropbox, webhooks, Chrome, and MCP.
- Full REST API Every option is a parameter, with NPM, PyPI, and RubyGem packages.
- Custom headers and cookies Send your own headers, cookies, user agent, language, and time zone.
Screenshots in Power Automate, answered.
Create a free PagePixels account, add the PagePixels Screenshots connector to your flow, connect it, and pick one of the four actions: take a screenshot of a web page, take one from a real geolocation, take one of custom HTML, or take one and analyze the image with AI. The action returns a file the rest of the flow can use.
Four published actions: capture a web page, capture from a real geographic location, capture custom HTML, and capture with AI analysis. Microsoft's connector reference lists the fields each one accepts, and it is the right source to check before you build against a specific parameter.
Yes. The connector, and every other integration, is on every plan including the free one. There are no connector tiers and no per-destination fees. The free plan is 25 screenshots a month with no credit card and no phone number.
Yes, through multi-step capture, which is part of the capture engine on every plan: log in, click links, fill out forms, run custom scripts, then capture. Build the step list in the web app or the API and the connector calls the same engine, so an internal dashboard or supplier portal arrives as the real page.
Yes, with the custom HTML action. Pass the message body to it and the connector renders it into an image, which is how an invoice or report email becomes something you can file in OneDrive or post to a channel rather than a thread someone has to dig through.
That is a separate integration with its own page: it lets Copilot agents capture websites with the same screenshot options. If you are automating a process, use this connector; if you are giving an agent the ability to look at pages itself, start there.
