Block 1 - Get screenshots
- Type / Role
- n8n-nodes-base.httpRequest - httpRequest
- Config choices
- Version 4.2
This workflow is provided as-is. Please review and test before using in production.
Capture URL Screenshots Automatically from Google Sheets & Drive with ScreenshotOne & Gmail Alerts Summary This automation template streamlines the process of capturing screenshots for multiple URL...
n8n-nodes-base.httprequest, n8n-nodes-base.googlesheets, n8n-nodes-base.googledrive, n8n-nodes-base.googledrivetrigger, n8n-nodes-base.gmail, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Niko.
Original n8n.io sourceThis automation template streamlines the process of capturing screenshots for multiple URLs. Instead of manually visiting each URL, taking a screenshot, and organizing the results, this workflow automates everything. When a spreadsheet is added to a designated Google Drive folder, the template extracts URLs from the column named "Url." These URLs are then processed through ScreenshotOne to capture screenshots, which are saved back to the same folder. Finally, an email notification is sent via Gmail with a link to the folder containing the screenshots.
This template addresses the challenge of manual screenshot capture for multiple URLs. Without this automation, a user would need to:
These steps are not only time-consuming but also repetitive, especially when handling a large number of URLs.
--YOUR ACCESS KEY-- with your generated access key in the "Get Screenshots" node.The workflow is set to monitor a specific Google Drive folder. It can be customized by selecting a different folder in the node settings.
While the template expects a spreadsheet with a column named "Url." for extracting URLs, users can add additional columns (e.g., titles, categories, or tags) and modify the workflow to utilize them as needed.
Customize the recipient, subject, and body of the notification email to suit your needs. If required, enable optional notifications for different stakeholders.
A valid ScreenshotOne Access key is required to capture screenshots. Users can further refine screenshot settings (e.g., viewport size, device emulation, or delay timing) by exploring the available options in the ScreenshotOne API documentation.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Capture URL screenshots from Google Sheets with ScreenshotOne & save to Drive with Gmail alerts |
|---|---|
| Complexity | intermediate |
| Nodes | 9 |
| Categories | File Management |
| Author | Niko |
| Published | 25 Mar 2025 |
Use the JSON export at /data/workflows/3321/3321.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Capture URL Screenshots Automatically from Google Sheets & Drive with ScreenshotOne & Gmail Alerts Summary This automation template streamlines the process of capturing screenshots for multiple URL...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your File Management use case.