ActionScreenshotOneUpdated September 2026

How do I take a webpage screenshot?

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.

ScreenshotOne Take Screenshot in ScreenshotOne — start free
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
URL
url
urlRequiredURL. e.g. "https://example.com"
Width
viewport_width
numberOptionalWidth
Height
viewport_height
numberOptionalHeight
Format
format
optionsOptionalFormat. Options: PNG, JPEG, WebP
Full Page
full_page
booleanOptionalFull Page
Sample request
{
"url": "https://example.com",
"viewport_width": "{{trigger.viewport_width}}",
"viewport_height": "{{trigger.viewport_height}}",
"format": "{{trigger.format}}",
"full_page": "{{trigger.full_page}}"
}
Returns
{
"store": {
"location": "https://cdn.screenshotone.com/..."
},
"cache_url": "https://cdn.screenshotone.com/..."
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for ScreenshotOne Take Screenshot.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about ScreenshotOne Take Screenshot.

What does the ScreenshotOne Take Screenshot action do in ScreenshotOne?
Returns a PNG or JPEG of a URL with viewport/device emulation, ad-blocking, JS rendering. For OG image generation, design audits, social media previews, presentation slides.
What inputs does ScreenshotOne Take Screenshot require?
Required: URL. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if ScreenshotOne returns an error?
The run history shows the failed step with its input and the error message ScreenshotOne returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does ScreenshotOne Take Screenshot support batch operations?
Run ScreenshotOne Take Screenshot inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within ScreenshotOne's rate limits.
ScreenshotOne Take Screenshot in ScreenshotOne — start free