Integrations
Screenshot integrations for the apps you already run.
Take, send, and save automated screenshots in Zapier, Make, n8n, Power Automate, Slack, Dropbox, Chrome, your own webhook, or a native MCP server. All of them are on every plan, including the free one.
25 free screenshots / month · no credit card · no phone number
every hour · Real Location: Germany
watch selector .plan-price
- Slack Message the channel, but only when .plan-price moves
- Dropbox PNG filed into a dated folder, every run
- Webhook JSON to your endpoint: image URL, diff, timestamp
- CDN embed One permanent link that always shows the latest
Ten integrations, maintained by the PagePixels team.
Each one carries the whole product: multi-step capture, scheduling, change alerts, Real Locations, and AI analysis. Nothing is API-only and nothing waits for a higher plan.
-
Slack
by pagepixels
Post scheduled screenshots into a private or public channel, or only when the page you are watching actually changes.
Learn more → -
Dropbox
by pagepixels
Save every scheduled capture straight into your Dropbox, filed into dated folders without a step in between.
Learn more → -
Custom Webhook
by pagepixels
POST the capture, the change notification, or the AI analysis to any endpoint you control, in JSON.
Learn more → -
Screenshot MCP
by pagepixels
Give an AI agent the whole capture suite behind one server URL: snap, schedule, watch, and read back what changed.
Learn more → -
Zapier
by pagepixels
Trigger captures from anything and send the image on to 7,000+ apps. Works as both the start and the end of a Zap.
Learn more → -
Make
by pagepixels
Capture live pages or your own HTML inside a Make scenario, with every option available as a module field.
Learn more → -
n8n
by pagepixels
Automate captures inside self-hosted n8n workflows, so the data and the schedule stay on your own infrastructure.
Learn more → -
Power Automate
by pagepixels
Drop web page captures into Microsoft 365 flows, ready to file in SharePoint, Teams, or an approval step.
Learn more → -
Copilot Studio
by pagepixels
Let your Copilot agents capture websites with 20+ screenshot options, without you writing the plumbing.
Learn more → -
Chrome Extension
by pagepixels
Capture the tab you are looking at, then turn that same capture into a scheduled watch in one click.
Learn more →
Three platforms maintain a PagePixels connector themselves.
These are maintained by the platforms, not by us, so their connector lists and pricing are theirs. If you already automate inside one of them, this is the shortest route in: the capture options are the same ones the API takes.
No matter how you use PagePixels, the engine behind it does not change.
A schedule built in the web app, a POST from your server, a Zap, or an agent tool call all reach the same browser session and the same archive.
-
Web app
no codeBuild the steps point-and-click, set the interval, and pick the destinations. The archive fills up on its own.
Control Panel → new config -
Screenshot API
restEvery option is a parameter, with NPM, PyPI, and RubyGem packages ready to drop in.
POST /screenshot_configs -
No-code platforms
5 appsZapier, Make, n8n, Power Automate, and Copilot Studio, so a capture can start or finish a workflow you already run.
trigger · action · both -
MCP server
agentsEvery endpoint exposed as a native tool over Streamable HTTP with OAuth 2.1, so an agent can set up a watch itself.
mcp.pagepixels.com
An integration is only useful if the payload is.
Most tools hand a downstream app one thing: an image. A capture here arrives with the context around it, so the Zap, the Slack message, or the agent on the other end can act without a second lookup.
Change notifications carry the same payload, which is what makes a one-step automation possible: capture, notice the difference, post the before and after into the channel.
-
The imagePNG, JPEG, WebP, or PDF at the size and scale factor you asked for, full page or one selector.
direct_link -
A permanent CDN linkAlways resolves to the latest capture of that config, with no API key in the URL.
embed_url -
The archive entryDated and listable through the API, so the delivery is not the only copy.
id -
What changedOn a change alert, the watched selector with its previous value beside the new one.
previous_value · retrieved_value -
The AI answerIf you asked a question of the capture, the written answer travels with the image.
ai.ai_response -
Where it captured fromWhether a Real Location was used for the capture, and which one.
proxy_server
Whichever integration you wire up, it can use all of these features.
Most screenshot APIs gate geolocation, scheduling, or output formats behind a higher tier. Nothing here is gated, on any plan.
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.
Questions people ask about wiring this up.
No. Every integration on this page, including the MCP server and the API, works on the free plan. There are no connector tiers, no per-destination fees, and no limit on how many destinations one capture goes to. The only thing a paid plan changes is how many screenshots you take.
No. Scheduling is built in, from every five minutes to once a year, and it runs whether or not any integration is connected. Use Zapier or Make when a capture needs to start from something else, or when the image has to end up somewhere we do not connect to directly.
Yes. A single config can post to Slack, save to Dropbox, and hit your webhook on the same run, and the capture is still filed in the archive with a permanent CDN link. Delivery is a list, not a single choice.
Either. A scheduled capture can send on every run, or you can watch a selector and send only when it moves, with the previous and new values in the payload. On a page that changes twice a year, that is the difference between 365 messages and two.
JSON with the image URL, the permanent CDN link, the archive id, the timestamp, and, when they apply, the change detail, the AI analysis text, and the rendered HTML. It is the same shape whichever destination receives it.
Yes, hosted at mcp.pagepixels.com over Streamable HTTP with OAuth 2.1. It exposes the whole API as native tools, so an agent can capture a page, create a scheduled watch, list the archive, and read back change notifications on its own. It is on every plan, free included.