Short answer: You can screenshotone take screenshot in ScreenshotOne by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the ScreenshotOne ScreenshotOne Take Screenshot action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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.