n8n Integration
Self-hosted workflow automation with n8n for teams that need full control over their data. Use the HTTP Request node to call the Screenshotly API, schedule recurring captures, and store results in your own infrastructure. Ideal for privacy-sensitive environments and air-gapped networks.
Quick Start
Set up your account
Install n8n locally with npm install -g n8n or use n8n Cloud at n8n.io.
Add HTTP module
Add an HTTP request module to make API calls.
Configure the request
Set up the POST request with Screenshotly API endpoint and authentication.
Connect your apps
Link the screenshot output to your destination apps.
Setup Steps
Add an HTTP Request node to your workflow
Configure it as a POST request to the Screenshotly API
Add headers for authentication and content type
Set up the JSON body with your screenshot options
Connect to file storage or other processing nodes
Execute or schedule your workflow
When to Use n8n with Screenshotly
Use the n8n integration when you need full control over your automation infrastructure — self-hosted, open source, and air-gapped compatible. n8n is the right choice for teams with strict data residency requirements, organizations that cannot send data through third-party SaaS platforms, or developers who prefer visual workflow editors with code-level flexibility.
n8n Best Practices
Use n8n's Credentials feature to store your API key once and reference it across multiple workflows.
Set the HTTP Request node's 'Response Format' to 'File' to properly handle binary screenshot data.
Use the IF node to check HTTP status codes and route failures to a Slack/email notification node for alerting.
For high-volume captures, use the SplitInBatches node with a batch size that matches your API rate limit.
n8n: Production Notes
n8n's core advantage over Zapier and Make is self-hosting. Your URL list, captured images, and credentials never leave your infrastructure. For industries with data residency or compliance requirements (financial services, healthcare, EU with strict GDPR posture on US-hosted automation), n8n is often the only viable option.
The second advantage is cost. n8n Community Edition is free for self-hosted single-user deployments. Make and Zapier price per operation; n8n prices per execution on Cloud or not at all on self-hosted. For workflows with >20k captures/month, the cost delta is thousands of dollars per year.
The trade-off is operational burden. You own the Docker container, Postgres database, backup strategy, and upgrades. n8n Cloud removes this but re-introduces per-execution pricing. The pragmatic choice: self-host when volume justifies the DevOps time; n8n Cloud for teams who need n8n's feature set without the hosting overhead.
Error Handling Recipes
Concrete strategies for each failure mode. Do not silently swallow errors — surface them to your monitoring so the pipeline is observable.
HTTP 429
Configure "Retry On Fail" in the HTTP Request node with exponential backoff. n8n respects the response status and retries automatically.
// In the HTTP Request node settings:
// Retry On Fail: true
// Max Tries: 3
// Wait Between Tries: 2000ms (exponential)Binary data handling
Set "Response Format" to "File" in the HTTP Request node. n8n passes the binary natively to downstream nodes (Write Binary File, S3 Upload, Google Drive Upload).
Queue workflow failure
n8n's Queue mode (Redis-backed) survives restarts. Enable it for critical production workflows — default memory mode loses in-flight work on restart.
Production Hardening Checklist
The difference between dev code and prod code. Work through these before putting n8n captures on a critical path.
- n8n credentials store holds the API key — never committed to workflow JSON.
- HTTP Request node configured with Retry On Fail and Response Format: File for binary.
- Queue mode enabled for production workflows.
- Postgres database backed up daily (automated cron or built-in).
- n8n Docker image pinned to a specific version, not :latest.
- Error Trigger workflow routes failures to Slack/PagerDuty.
- Self-hosted deployment behind auth (basic auth minimum, SSO on Enterprise).
Rate-Limit Strategy
Self-hosted n8n has no artificial rate limit — you can overwhelm Screenshotly if careless. Use Split In Batches (batch size 5–10) plus a Wait node of 1–2s between batches. For high volume, run multiple worker instances with Redis-backed Queue mode and configure executions.concurrency.
When n8n isn't the right fit
n8n works well for most capture workloads, but these patterns are legitimate reasons to pick a different stack:
- Your team has no DevOps capacity to maintain a self-hosted Docker container, Postgres database, and backup strategy. n8n Cloud removes that burden but brings per-execution pricing similar to Make.
- You need instant setup with zero infrastructure. Zapier or Make's hosted offerings are simpler; n8n requires more upfront configuration even on Cloud.
- Your workflow integrates with dozens of proprietary SaaS apps that have Zapier-native triggers but no n8n nodes. n8n's integration library is strong but not as broad as Zapier's.
Want a step-by-step walkthrough?
Read the full n8n tutorial →API Reference
POST /api/screenshotBearer tokenapplication/jsonFrequently Asked Questions
Why use n8n with Screenshotly instead of Zapier or Make?
n8n is self-hosted and open source, so your screenshot data and API keys never leave your infrastructure. It's ideal for teams with compliance requirements, air-gapped environments, or those who want to avoid per-task SaaS pricing.
How do I handle errors in n8n screenshot workflows?
Use n8n's Error Trigger node to catch failed HTTP requests. Set up retry logic with the Wait node and an IF condition that checks the response status code. Route failures to a notification channel (Slack, email) for manual review.
Can I run n8n screenshot workflows on a schedule?
Yes. Use the Cron or Schedule Trigger node to run your workflow at fixed intervals. For example, capture competitor website screenshots every morning at 8 AM or archive a list of URLs every Sunday night.
How do I process multiple URLs in a single n8n workflow?
Use the Spreadsheet File node or Set node to define a list of URLs, then connect to the HTTP Request node. n8n automatically iterates over the list, capturing a screenshot for each URL. Add a Wait node between requests to respect rate limits.
Start building with n8n
Get your API key and start capturing screenshots in minutes.
Other Platforms
Zapier
Connect Screenshotly with 5,000+ apps through Zapier using the Webhooks action. Automate screenshot workflows without writing code — capture pages when Google Sheets rows are added, save screenshots to Drive on form submissions, or post visual updates to Slack on a schedule.
Make (Integromat)
Build visual automation workflows with Make (formerly Integromat) using the HTTP module. Create complex screenshot pipelines with drag-and-drop — schedule captures, route results to multiple destinations, and chain screenshot operations with data transformation steps.