n8n's HTTP Request node speaks to the Screenshotty API natively. Feed it URLs from any source node (webhook, schedule, database, RSS), and pass the captured image to Slack, S3, Telegram, or your own service in the next node.
Use header auth with your API key stored as an n8n credential, and response_type=json so the image URL lands in the item's JSON for easy mapping — or binary response mode if you want the file itself in the workflow.
// Method: POST// URL: https://api.screenshotty.link/api/v1/screenshot// Authentication: Generic → Header Auth// Name: X-Api-Key Value: {{ $credentials.screenshottyKey }}// Body Content Type: JSON{"url": "={{ $json.pageUrl }}","full_page": true,"adblock": true,"response_type": "json"}// Response: JSON → $json.url holds the screenshot URL
The built-in HTTP Request node is all you need, on n8n cloud or self-hosted.
Take the raw image into n8n's binary data for file operations, or a hosted URL for messaging steps.
Map over a list of URLs with Split In Batches for bulk capture runs with rate control.
Capturing happens on Screenshotty's fleet, so your n8n instance stays light — no Chrome container.
Set the HTTP Request node's response format to File (binary) instead of JSON-mode, then connect an S3 / Write Binary File node — the image flows through as binary data.
Use a Schedule Trigger (cron) into the HTTP Request node. Add an IF node + image diff service if you want change alerts.
Sign up at screenshotty.link (free tier: 100 screenshots/month, no credit card) and copy your key from the dashboard. Keep it in the integration's credential store rather than pasting it into shared workflows.
Use Split In Batches with a small batch size and a Wait node between batches; your plan's rate limit is documented in the dashboard.