Zapier Screenshot Integration: No-Code Workflows
Set up a Zapier workflow that captures a URL with Screenshotly and saves the image to Google Drive, Dropbox or any app with a file field.
Zapier has no Screenshotly app, but its Webhooks by Zapier tool can call any HTTP API. This guide sets up a Zap that captures a web page and passes the image to Google Drive, Dropbox, Slack or any other app with a file field.
The most important detail is the response. The Screenshotly API normally returns the image bytes directly, and Zapier doesn't document how Webhooks by Zapier handles a binary response. So this guide uses the API's storage option, which returns a small JSON response with a download link that Zapier's file fields can use.
What you need on each side
| Requirement | Why | |
|---|---|---|
| Zapier | A paid plan (Professional or above) | Webhooks by Zapier, multi-step Zaps, Paths and Autoreplay are not on Zapier's Free plan. |
| Screenshotly | Basic plan or above | storage (a signed download link) and webhook delivery start on Basic. The free plan returns image bytes only. |
If you're on Screenshotly's free plan, test the request shape with curl or the playground first, then upgrade when you're ready to automate in Zapier. For the free plan, Make and n8n can store the binary response directly.
Step 1: Choose a trigger
Any trigger that gives you a URL works. For example:
- Google Sheets: new row with a URL column.
- RSS by Zapier: new item in a feed (map the item link).
- Schedule by Zapier: every day or week, with a fixed URL.
- Form tools such as Typeform or Google Forms: a URL field in the submission.
Step 2: Add the capture step
-
Add an action step, choose Webhooks by Zapier, and pick the Custom Request event.
-
Method:
POST -
URL:
https://screenshotly.app/api/screenshot -
Data:
{ "url": "https://example.com", "width": 1280, "height": 800, "fullPage": true, "format": "png", "storage": { "enabled": true } }Replace
https://example.comwith the URL field from your trigger, keeping the quotation marks around it. -
Headers:
Key Value x-api-keyyour Screenshotly API key Content-Typeapplication/json
Use Custom Request rather than the POST event. Zapier sends Custom Request data exactly as you typed it, so you control the JSON: numbers and true stay numbers and booleans, and storage stays a nested object. The API's schema is strict. It rejects a width sent as the text "1280", unknown fields such as viewport, and values outside the allowed ranges.
Test the step
Click Test step. A successful response looks like this:
{
"success": true,
"url": "https://screenshotly.app/api/assets/…?expires=…&signature=…",
"format": "png",
"size": 48213,
"duration": 2140
}
The url is a signed link that works for 24 hours. The file itself is kept for your account's retention period (7 days by default, adjustable from 1 to 30 days). It is not a permanent public URL.
Step 3: Save the file
Add the destination app and map the Url field from the capture step into its File field. When a file field gets a public, direct-download URL, Zapier loads the file from it and uploads it, and the signed link is that kind of URL. Set the file name explicitly where the app allows it, for example a date from the trigger followed by -homepage.png.
Common destinations are Google Drive → Upload File and Dropbox → Upload File, but any action with a File field works the same way.
Zapier must be able to retrieve a file within 30 seconds, which is not a problem for a single screenshot.
Example Zaps
Daily snapshot of a pricing page
-
Trigger: Schedule by Zapier, every day at 09:00.
-
Action: Webhooks by Zapier, Custom Request, as above, with:
{ "url": "https://competitor.example/pricing", "width": 1440, "height": 900, "fullPage": true, "blockAds": true, "storage": { "enabled": true } } -
Action: Google Drive, Upload File, File =
Url, into a "Pricing snapshots" folder.
blockAds works on every plan. It blocks known ad requests and hides common ad and cookie-banner elements. To hide chat widgets and popups with AI element removal, add "aiRemoval": { "enabled": true, "types": ["cookie-banner", "chat-widget"] }, which needs the Growth plan.
Screenshot of each new blog post for social scheduling
- Trigger: RSS by Zapier, New Item in Feed.
- Action: Custom Request with
{ "url": "<item link>", "width": 1200, "height": 630, "format": "png", "storage": { "enabled": true } }. - Action: Dropbox, Upload File, File =
Url, then pass the Dropbox link to your social tool.
For an image designed for social sharing, capture a dedicated template page rather than the article itself. See the dynamic OG image guide.
PDF record of a form submission's page
- Trigger: your form tool, with a hidden field holding the page URL.
- Action: Custom Request with
{ "url": "<hidden field>", "format": "pdf", "storage": { "enabled": true } }. - Action: Google Drive, Upload File.
PDFs need Basic and always print on A4 with 1 cm margins.
Slow pages: a two-Zap pattern
Zapier doesn't document a fixed timeout for webhook steps, and a capture can take up to about 30 seconds. If a page is slow, or you capture many URLs, queue the work and let Screenshotly call Zapier back when it's done:
Zap 1: queue the capture
-
Custom Request,
POSTtohttps://screenshotly.app/api/jobs, with the same headers and this data:{ "url": "https://example.com", "fullPage": true, "format": "png", "webhook": { "url": "https://hooks.zapier.com/hooks/catch/…" } }The webhook URL is the one Zapier gives you in Zap 2. The API answers
202with a jobidstraight away.
Zap 2: receive the result
- Trigger: Webhooks by Zapier, Catch Hook.
- Filter: continue only if
eventisscreenshot.completed. Failed jobs sendscreenshot.failedwith anerrorfield, so you can route those to a notification instead. - Action: Google Drive, Upload File, with File set to the payload's
data→storageUrlvalue (Zapier usually labels it Data Storage Url).
The completed payload looks like this:
{
"event": "screenshot.completed",
"timestamp": "2026-11-13T09:00:12.000Z",
"data": { "url": "https://example.com", "format": "png", "size": 48213, "storageUrl": "https://screenshotly.app/api/assets/…", "duration": 8120 }
}
Async jobs need Basic. Each job gets up to three attempts before the failure webhook is sent. If you add a webhook.secret, Screenshotly signs each delivery with an X-Screenshotly-Signature: sha256=… header, but a Catch Hook can't verify it without a Code step. Keep the hook URL private instead.
Capturing many URLs
- Looping by Zapier can run the capture step once per row or list item.
- Mind the API's per-minute limit: 40 requests per minute on Basic, 80 on Growth and 200 on Scale. Add Delay by Zapier inside the loop if you are close to it.
- Every capture counts toward your monthly quota (2,500 on Basic). Failed captures don't.
- For more than a handful of URLs, the async pattern above is more reliable than a long synchronous loop.
When something fails
Zapier marks the step as errored and stops that run. The API's JSON error says why:
| Status | error |
Fix |
|---|---|---|
| 400 | Invalid request data | Check field names and types. A common cause is a number or true/false sent as text. |
| 400 | Unsafe URL | The URL is private, local or not HTTP(S). |
| 401 | Authentication failed | Check the x-api-key header. |
| 403 | Plan upgrade required | The option (for example storage on the free plan) needs a higher plan; see minimumPlan. |
| 429 | Rate limit exceeded | Per-minute rate or quota reached. Check message and the Retry-After header. |
| 500 | Screenshot generation failed | The page blocked automation, failed to load in 30 seconds, or errored. |
On paid Zapier plans you can turn on Autoreplay, which replays errored runs, or attach a custom error handler to the step, for example to post the failed URL to Slack. A Zap can't use both at once. Replays only help with temporary failures such as a 429 or 500.
Keep the key safe
The API key sits in the step's headers. Anyone who can edit the Zap can see it, so share Zaps carefully, and rotate the key from your Screenshotly dashboard if it leaks.
Ready to connect Screenshotly to Zapier?
Create a free API key → to test requests, then upgrade to Basic for storage links.
See also:
About the Author

Asad Ali
CTO at ZTABS and the developer behind Screenshotly. Writes about screenshot automation, API design, and building reliable SaaS backends with Next.js, Node.js, and TypeScript.
Credentials: CTO at ZTABS, full-stack developer, builder and maintainer of Screenshotly and its official JavaScript and Python clients
Frequently Asked Questions
Is there a Screenshotly app in Zapier?
No. You call the API with Webhooks by Zapier, which Zapier includes on its paid plans (Professional and above) but not on the Free plan.
Why use the storage option instead of the image response?
Without it, the API returns the raw image bytes, and Zapier does not document how Webhooks by Zapier handles a binary response. With storage enabled (Screenshotly Basic and above), the API returns JSON with a signed download URL, and Zapier file fields can load a file from a public URL.
What happens if Screenshotly returns an error in the middle of a Zap?
Zapier marks the step as errored and stops that run. On paid Zapier plans you can turn on Autoreplay, or add a custom error handler to the step. You can't use both on the same Zap. Retrying won't fix a 400 or 403, so check the error message first.
Ready to capture your first screenshot?
Get started with 100 free screenshots. No credit card required.