PagePixels Screenshots
Developer ToolsCapture, schedule, and monitor website screenshots with the PagePixels Screenshot API, including rendering raw HTML into images. Agents keep visual evidence of what a page looked like when it mattered.
What This Integration Enables
Most page monitoring answers "did this change?" PagePixels answers a different and often more valuable question: "what did this look like at a moment I can point to?" A screenshot configuration captures on a recurring schedule, archives every capture, and exposes a permanent embed URL that always serves the latest one. List Configuration Screenshots returns each capture with its own timestamp and job ID. That is an evidence trail, and evidence is what you need when a customer, an auditor or a client disagrees with you about what a page said.
The capture surface is deep enough to reach pages a plain fetch cannot. Multi step browser actions log in, fill forms and click through a site before the shot is taken. Captures can be geolocated through a proxy network, sized to a chosen viewport, and returned as JPEG, PNG, WebP or PDF. Screenshot From HTML renders raw markup into an image with no hosted page at all, which turns a generated report or an email template into a shareable asset from inside the flow that produced it. Extract Page HTML returns fully rendered markup for single page applications that plain HTTP requests read as empty. And Analyze Images With AI runs prompts across up to five images at once, including images PagePixels did not capture, for visual regression checks and text extraction. FlowRunner connectors make all of that callable from a workflow, and the agent holds the capture while a person decides what it proves.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Screenshot evidence attached to a dispute
A customer opens a ticket arguing that a promotion was advertised differently than it was honoured. Because a scheduled configuration has been capturing that landing page hourly, the agent lists the archived captures, finds the ones bracketing the signup timestamp, saves the matching image into FlowRunner file storage, and attaches it to the ticket in Zendesk with the capture time stated plainly. The support agent gets the artifact and the timestamp together, and decides the case on what the page showed rather than on what anyone remembers.
Branded report images generated from workflow data
An agency produces a weekly client summary. Rather than exporting charts by hand, the flow assembles the numbers, builds the HTML for a branded card, and calls Screenshot From HTML to render it at the right viewport and scale factor. The resulting image goes straight into the client email and into the shared drive via Google Drive. Nothing is designed twice, and the image always reflects the data the same run produced.
Competitor and status page change watching with a picture attached
A configuration with a change action watches a competitor's price element. When On Change Detected fires with the previous and new values, the agent pairs the values with the capture that produced them and posts both into Slack. List Account Change Notifications gives the same team a single audit view of every watched element across every configuration, which is where a quarterly review actually starts rather than a search through months of alerts.
Human-in-Loop Highlight
The consequential operation on this connector is Delete Screenshot Configuration, and it is more consequential than its name suggests. Deleting a configuration permanently deletes every screenshot it ever captured, stops its schedule, and invalidates its embed URL. So a routine cleanup pass over stale configurations can, in one call, destroy the only dated record of what a page looked like during a period someone is currently disputing, and simultaneously break every place that embed URL was pasted: a client dashboard, a status page, a support macro.
An agent running retention cleanup therefore never deletes on its own. It gathers the facts first, then stops: "Configuration 'EU pricing page hourly' holds 2,140 archived captures spanning the last 90 days and its embed URL is live. Deleting removes every capture and breaks the embed. Delete, or pause the schedule and keep the archive?" A person answers. This is the digital andon cord applied to evidence retention: the agent has enough information to know the deletion is irreversible, so it stops the line rather than optimising storage against a record somebody may need. A related trap sits on Update Screenshot Configuration, where omitting the Scheduled option converts a recurring configuration back to a one time capture, quietly ending the archive without deleting anything, so agents supply that option explicitly on every update to a scheduled configuration.
Agent Capabilities
17 actionsScreenshots
4- Take Screenshot Captures an immediate screenshot of any public web page and returns CDN links to the full image and its thumbnail. Supports full page or single element capture by CSS selector, viewport sizing, JPEG, PNG, WebP and PDF output, geolocated capture through a proxy network, ad and cookie banner blocking, and optional AI analysis. Captures are cached for the TTL period and cached deliveries do not consume credits.
- Screenshot From HTML Renders raw HTML markup in a real browser and returns CDN links to the resulting image, with no hosted page required. Used to turn email templates, generated reports and third party API data into shareable images from inside the flow that produced them.
- Extract Page HTML Returns the fully rendered HTML of a page instead of an image, executing JavaScript first so dynamically generated markup is included. Provide an element selector to receive only that element's outer HTML. Used for reading single page applications that plain HTTP requests see as empty.
- Save Screenshot To File Downloads a PagePixels CDN image, such as a link returned by Take Screenshot or listed in the capture history, and stores it in FlowRunner file storage. Returns the FlowRunner file URL alongside the original CDN link.
Scheduled Screenshots
7- Create Screenshot Configuration Creates a persistent configuration that PagePixels captures on demand or on a recurring schedule, returning a permanent embed URL that always serves the most recent capture. Supports multi step browser actions to log in, fill forms and click through a site before capturing, plus change notifications posted to a webhook when a watched element changes.
- Update Screenshot Configuration Updates an existing configuration, for example to change the captured URL, adjust the schedule, or replace the multi step actions. The URL is required on every update, and Scheduled must stay enabled when updating a scheduled configuration or it reverts to a one time capture.
- Get Screenshot Configuration Retrieves a single configuration by ID with its current capture options, schedule, permanent embed URL, last job ID and creation timestamp. Used to inspect a configuration before updating it or to resolve the embed URL for display.
- List Screenshot Configurations Lists every configuration in the account with its options, schedule, embed URL and creation timestamp. Results are paged and can be narrowed to a creation window and sorted newest or oldest first.
- Delete Screenshot Configuration Permanently deletes a configuration together with every screenshot it has captured, stops its schedule and invalidates its embed URL. Returns the configuration as it existed at deletion time.
- Capture Next Screenshot Immediately queues a new capture for an existing configuration without waiting for its schedule, leaving the recurring schedule untouched. Returns a job ID plus the embed URL, and fails if a capture for the same configuration is still running.
- Get Job Status Checks whether the capture behind a job ID has finished and returns the CDN links and capture timestamp once it has. While the capture runs the API responds with an in progress error code, so poll until it succeeds.
Screenshot History
2- List Configuration Screenshots Lists every screenshot previously captured by one configuration with the full image link, thumbnail, capture timestamp and job ID. Results are paged and can be narrowed to a capture window. This is the action that turns an archive into a change timeline.
- List Account Screenshots Lists every screenshot captured across the whole account, including browser extension captures, with each record carrying its ID, owning configuration, embed URL, CDN links, timestamps and any AI analysis prompt and response.
Change Notifications
2- List Configuration Change Notifications Lists every change detected by one configuration's change actions, returning the previous value, the new value, the watched selector and when the notification was sent.
- List Account Change Notifications Lists every change detected across all configurations in the account, each record identifying the configuration, watched selector, previous and new values and send timestamp. Used to audit competitor price and content monitoring in one place.
AI Analysis
1- Analyze Images With AI Runs AI analysis over up to five image URLs using up to five prompts, returning one response per prompt. Prompts may target a single image or compare several, which suits visual regression checks, text extraction and captioning of images PagePixels did not capture.
Account
1- Get Account Limits Returns monthly allowances and current usage for screenshots, proxy bandwidth and AI Analysis credits. Used to guard an automation against exceeding its limit by checking remaining capacity before a large batch of captures.
Triggers
2 triggersEvent Triggers
2- On New Screenshot Fires when PagePixels finishes a new capture, either for one selected configuration or for every configuration in the account. Each event carries the CDN image link, thumbnail link, capture timestamp and job ID. The first cycle establishes a baseline and emits nothing, so existing captures are not replayed on activation.
- On Change Detected Fires when a change action on a configuration detects that a watched element has changed, carrying the previous value, the new value and the watched selector. Requires at least one multi step change action on the configuration. The first cycle establishes a baseline so past changes are not replayed on activation.
Frequently Asked Questions
What can FlowRunner do with PagePixels Screenshots?
FlowRunner agents can run Take Screenshot, Screenshot From HTML, and Extract Page HTML in PagePixels Screenshots, plus 14 more actions.
Does connecting PagePixels Screenshots to FlowRunner require OAuth?
No. PagePixels Screenshots connects to FlowRunner with an API key, no OAuth flow required.
Can PagePixels Screenshots trigger a FlowRunner workflow automatically?
Yes. PagePixels Screenshots supports 2 triggers that can start a FlowRunner workflow automatically.
Start building with PagePixels Screenshots
$100 in credits. No card required. Connect in minutes.