Package Information
Available Nodes
Documentation generating…
Documentation
n8n-nodes-websitescreenshotworld
n8n community nodes for Website Screenshot World: take
screenshots, PDFs, videos and the readable content of any web page, capture a scheduled page on demand, and start a
workflow when a capture finishes or a page changes.
Installation · Credentials · Operations · Trigger ·
Example workflows · Compatibility · Resources ·
Version history
Installation
In n8n, open Settings → Community Nodes → Install and enter:
@websitescreenshotworld/n8n-nodes-websitescreenshotworld
On a self-hosted instance started from the command line you can also runnpm install @websitescreenshotworld/n8n-nodes-websitescreenshotworld in ~/.n8n/nodes. See the
n8n guide to installing community nodes.
Credentials
Website Screenshot World has two products with keys of their own, and webhooks with a signing secret. Each has its
credential, so a workflow only holds what it uses.
| Credential | Used by | Where to get it |
|---|---|---|
| Website Screenshot World Instant Snap API | Capture operations | In the app, Developer Tools → API Keys, a key for Instant Snap. Starts with wsw_api_. |
| Website Screenshot World Auto Schedule API | Scheduled Page → Capture Now | Developer Tools → API Keys, a key for Auto Schedule. Starts with wsw_autoapi_. |
| Website Screenshot World Webhook API | The trigger | Developer Tools → Webhooks, the signing secret. Starts with whsec_. |
Test on a credential checks the key with the API. For the signing secret it checks only that the value has the
right shape, because a secret is never sent anywhere: it is used to check the signature of each delivery.
Operations
The Website Screenshot World node. It can also be used as a tool by an n8n AI agent.
Capture (Instant Snap API)
| Operation | What it does |
|---|---|
| Take Screenshot | PNG, JPEG, WebP or TIFF, of the viewport or the full page |
| Create PDF | An image PDF (the page as it looks on screen, full page or viewport) or a document PDF (selectable, searchable text, the visible part of the page) |
| Record Video | MP4, WebM, MOV or GIF of the page scrolling from top to bottom |
| Get Page Content | The main content of the page as Markdown or plain text, in the content field. Navigation, footers, cookie banners and scripts are left out, which makes it a good tool for an AI agent |
| Get | An earlier capture by its ID, optionally with its file |
Output chooses between the file itself, as binary data in the data field (ready for Google Drive, S3, email,
Slack and so on), and the capture details with a download link that works for 60 minutes. Files are kept for 24
hours.
Options cover what the API offers: device (desktop or an emulated phone), viewport size and scale factor, full-page
height limit, ad and pop-up blocking, pressing Escape, page timeout and scrolling delay, user agent, locale and time
zone, a proxy country, an element to capture by XPath, elements to hide, click or hover, a timestamp watermark, request
headers and cookies, geolocation, the page source alongside the capture, a callback URL and an idempotency key. The
emulated devices and proxy countries are loaded from the API, so the lists are always current.
Every option left unset keeps the API's default, which blocks ads and pop-ups and captures a 1920×1080 desktop
viewport. Saving to your own S3 bucket and asynchronous captures are not in the node; use the
HTTP Request node with the same
credential for those.
Scheduled Page (Auto Schedule API)
| Operation | What it does |
|---|---|
| Capture Now | Captures a web page that is scheduled in Auto Schedule now, outside its schedule, with all its settings, comparisons and deliveries |
For Web Page ID, paste the URL that the Trigger API badge on the web page in the app copies, or just the ID in
it. A trigger event carries the same ID as schedule_id. If a capture of the page is already queued or running, the
answer is already_pending and nothing new is started or charged.
When the API refuses
A refusal stops the node with the API's own message and its code, for example quota_exhausted, rate_limited
or validation_failed. Turn on Retry On Fail in the node settings to retry the temporary ones, and On Error →
Continue to handle refusals in the workflow: the item then carries an error field.
Trigger
The Website Screenshot World Trigger node starts a workflow when Website Screenshot World sends a webhook:
| Event | When |
|---|---|
capture.succeeded, capture.failed |
A capture finished or failed (Instant Snap and Auto Schedule) |
capture.changed |
A scheduled capture differs from the one before it, with change_percent |
delivery.completed |
A capture finished uploading to its cloud storage destinations |
schedule.paused |
A schedule was paused, for example because the plan ran out of captures |
sitemap_run.completed |
Every page of a sitemap schedule run has been captured |
ping |
A test delivery sent from the app |
The output is the event as sent: id, type, created_at, product and data.
Setting it up
- Add the trigger to a workflow and choose the Webhook API credential with your signing secret.
- Copy the trigger's Production URL.
- In the app, open Developer Tools → Webhooks → Add endpoint, paste the URL and tick the events to send.
- For Auto Schedule events, switch on Trigger webhook under After the capture in the Web Profile the schedule
uses. An endpoint alone is not enough. - Activate the workflow.
To try it in the editor first, use the Test URL instead, click Listen for test event, and press Send test on
the endpoint in the app, which sends a ping. Endpoints must be public https addresses, so an n8n running only on
your own computer needs a tunnel to receive deliveries.
Every delivery is checked against its X-WSW-Signature header before the workflow starts. A delivery with a missing,
wrong or more than five minutes old signature is answered with 401 and does not start the workflow. Deliveries of
events or products the trigger is not set to are answered with 200 and ignored, so they are not retried. A delivery
can arrive more than once; its id stays the same, so use it to skip repeats if that matters.
Example workflows
Save a full-page screenshot of every new page to Google Drive. RSS Feed Trigger → Website Screenshot World (Take
Screenshot, URL {{ $json.link }}, Full Page on) → Google Drive (Upload, binary field data).
Tell Slack when a competitor's pricing page changes. Schedule the page in Auto Schedule with comparisons on, then
Website Screenshot World Trigger (event Capture Changed) → If ({{ $json.data.change_percent }} > 5) → Slack.
Give an AI agent the web. AI Agent → tool: Website Screenshot World (Get Page Content) to read pages as Markdown,
and (Take Screenshot) to look at them.
Archive invoices as PDFs. Webhook → Website Screenshot World (Create PDF, Image PDF, Full Page on) → Email.
Compatibility
Built and tested with n8n 2.47 and @n8n/node-cli 0.55. Requires the Node.js version n8n itself requires.
Resources
- n8n community nodes documentation
- Instant Snap API reference
- Webhooks
- Client libraries for seven languages
- Support: support@websitescreenshotworld.com
Version history
See CHANGELOG.md.