Short answer: Drop the "ScreenshotOne → ScreenshotOne Take Screenshot" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
URL url | url | Required | URL. e.g. "https://example.com" |
Width viewport_width | number | Optional | Width |
Height viewport_height | number | Optional | Height |
Format format | options | Optional | Format. Options: PNG, JPEG, WebP |
Full Page full_page | boolean | Optional | Full Page |
{"url": "https://example.com","viewport_width": "{{trigger.viewport_width}}","viewport_height": "{{trigger.viewport_height}}","format": "{{trigger.format}}","full_page": "{{trigger.full_page}}"}
{"store": {"location": "https://cdn.screenshotone.com/..."},"cache_url": "https://cdn.screenshotone.com/..."}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.