n8n integration
Take website screenshots inside your n8n workflows.
Add the PagePixels node and a workflow can capture a page, act on it first, render another node's HTML as an image, ask AI what it says, or shoot from another country. Self-hosted or cloud, on every plan including the free one.
- Instant and multi-step captures inside any workflow.
- Send the images on to hundreds of n8n nodes.
- Turn raw HTML from another node into an image.
- Have AI analyse the capture in the same run.
- Capture from geographic locations around the world.
25 free screenshots / month · no credit card · no phone number
-
Trigger Every hour Schedule
-
Node Take a screenshot PagePixels
-
Node Insert the row Postgres
-
Node Post the image Slack
How to take a screenshot in n8n in four steps
If you have built a workflow before, skim this. The node behaves like any other in the canvas.
-
Create a free account
Sign up for PagePixels first, because the node connects to an account. Every feature is on the free plan.
25 screenshots / mo -
Add the PagePixels node
In the canvas, search for PagePixels Screenshots, drop it in after your trigger, and add your credentials once.
search: PagePixels -
Pick the action
A live URL, a multi-step capture for gated pages, custom HTML from an earlier node, AI analysis, or a capture from another location.
url · steps · html · ai -
Route the output
The node returns the image and its metadata as items. Send them to storage, a database, a chat node, or straight back out through your own API.
output → next node
Setup screens and field notes are in the n8n guide, and every action maps to a parameter in the Screenshot API if you would rather read it that way.
Five kinds of capture, in one node.
A live URL is the easy case. Past that, the node can work for its subject: log in, dismiss the banner, click into the tab, wait for the element, then shoot.
Custom HTML is the one that changes what a workflow can do. Raw HTML from an earlier node becomes the image, so a database row, an API response, or a rendered template turns into something a person reads at a glance rather than parses.
AI analysis and geographic capture are node options too, not separate products, so a workflow can ask what a page says and check how it looks in another market in the same run.
-
A live page
urlGive the node a URL and the size you want, and it returns the capture for the rest of the workflow to use.
-
A page that needs work first
multi-stepLog in, dismiss the consent wall, click into a tab, wait for an element, then capture, inside the same node.
-
HTML from another node
custom htmlRender a database row, an API response, or a template built earlier in the workflow into an image.
-
A capture the workflow can read
ai analysisAsk a question of the capture and get a written answer back with it, so a later node can branch on the content.
-
A page in another market
geolocationCapture through a location around the world so geo-gated pricing and consent screens render the way locals see them.
The reason people self-host is also the reason this node is useful.
Running n8n yourself keeps the workflow, the credentials, and the data on your own infrastructure. The awkward part is rendering: a real browser per capture means Chromium in a container, memory spikes, fonts, timeouts, and proxies to maintain.
The node hands that one job out and keeps everything else where it was. No Chromium image to keep patched, no queue for slow renders, no residential proxy contract of your own.
And what comes back is not just a file: the same capture is kept in a dated archive here with a permanent link, so a workflow that fails to write its copy has not lost the record.
- Chromium in a container to patch No browser to install or update
- Memory spikes on heavy pages Renders happen off your instance
- Your own proxy contract for geo checks 150+ locations included
- Login flows scripted by hand Multi-step actions as node parameters
- Images live only where you wrote them Also kept in a dated archive here
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 workflow running. Use n8n when the capture has to start from something else in your stack, or when the image has to land somewhere we do not integrate with directly.
A workflow that captures a login screen hourly is worse than no workflow.
The pages worth automating are usually gated: a dashboard behind a login, a report you have to generate, a consent wall in the way. A renderer that only accepts a URL returns the wrong screen, reliably, forever.
Multi-step screenshots are part of the n8n integration, not a web-app-only feature. Fill the fields, submit, wait for the element, then capture, all inside the one node. Available point-and-click in the app or as parameters here, on every plan.
Captures can also run through a Real Location in 150+ countries, states, and cities, so a geo-gated page reaches your workflow the way a local customer sees it.
-
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 items to the workflow node output
Four workflows worth ten minutes
Each is a trigger node, one PagePixels node, and somewhere in your own stack for the result to land.
-
Schedule → PagePixels → Postgres
A visual record beside the data
Capture the page hourly, write the row, and keep the image alongside it so the number in the database always has a picture to back it up.
hourly · insert row -
Webhook → PagePixels → S3 node
Captures on demand from your app
Your own service calls an n8n webhook, the node captures the page, and the workflow stores it wherever your stack already keeps files.
on request · your storage -
Postgres → PagePixels → email
Reports as pictures, not attachments
Build the HTML from a query result, render it as an image, and send a report that reads at a glance on a phone.
custom html · weekly -
PagePixels → AI → IF node
Let the workflow decide
Capture a page, ask the AI whether anything material changed, and branch on the answer instead of alerting a human every run.
ai analysis · branch
The n8n integration is not a lite version.
This list is the same on the free plan and the largest one, and the same through the node, 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 n8n, answered.
Create a free PagePixels account, add the PagePixels Screenshots node to your workflow, add your credentials once, and choose the action: a live URL, a multi-step capture, custom HTML from an earlier node, AI analysis, or a capture from another location. The node returns the image and its metadata as items for the next node.
Yes, and that is the common case. The workflow, the credentials, and the data stay on your instance; the page render happens on our side, so you do not need Chromium in your container or a proxy contract of your own.
Yes. The n8n integration, and every other one, 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. Multi-step actions run inside the node: fill the fields, submit, wait for the element to appear, then capture. They are the same thirteen action types the web app and the API use, so a gated dashboard reaches the workflow as the real page.
Yes, with the custom HTML action. Build the markup from a query result, an API response, or a template earlier in the workflow, and the node returns an image with every capture option still available. It is how a JSON payload becomes something a person will actually read.
No. Scheduling from every five minutes to once a year, change detection, and delivery to Slack, Dropbox, or a webhook are built in, so captures can recur with no workflow running. Use n8n when the capture has to start from something else in your stack, or when the result has to land in a system we do not integrate with directly.
