How to Automate Screenshots with Zapier (No Code Required)

Zapier connects 6,000+ apps and lets you build automations without writing code. SnapSharp is a REST API that returns screenshots as images — and it works with Zapier out of the box via the Webhooks by Zapier action. No dedicated Zapier app, no approval process, no waiting.

This guide walks through the most common Zapier + SnapSharp workflows with exact field values you can copy.

What you need

• A SnapSharp account (free tier: 100 screenshots/month)
• Your API key from Dashboard → API Keys
• A Zapier account (free plan works)

Step 1: Add the Webhooks by Zapier action

In any Zap, after your trigger step:

1. Click + to add an action
2. Search for Webhooks by Zapier
3. Choose Custom Request as the event

"Webhooks by Zapier" is available on Zapier's free plan.

Step 2: Configure the request

Screenshot a URL (GET)

This is the most common use case — turn any URL into a PNG/JPEG image.

Query String Params (add each as a separate row):

Set Response type to File so Zapier treats the response as binary image data (not JSON).

Generate an OG Image (POST)

To generate an Open Graph image from a template:

Request body:

{
  "template": "blog-post",
  "data": {
    "title": "{{title from trigger}}",
    "author": "{{author from trigger}}"
  },
  "width": 1200,
  "height": 630
}

Step 3: Use the image in later steps

Once the Webhooks step runs, Zapier gives you the image as a file object. You can pass it directly to:

• Google Drive → Upload file
• Dropbox → Upload file
• Gmail → Send email with attachment
• Slack → Send file to channel
• Notion → Upload to a page
• Airtable → Attach to a record

Real Zap examples

New blog post → screenshot → save to Drive

Trigger: RSS by Zapier — New item in feed
Action 1: Webhooks by Zapier — GET https://api.snapsharp.dev/v1/screenshot?url={{link}}&width=1280&format=png
Action 2: Google Drive — Upload file → use the file from Action 1

New Airtable row → screenshot URL → attach to record

Trigger: Airtable — New Record
Action 1: Webhooks by Zapier — GET screenshot of {{URL field}}
Action 2: Airtable — Update Record — Attachments field → file from Action 1

Shopify order → screenshot product page → email to team

Trigger: Shopify — New Order
Action 1: Webhooks by Zapier — GET screenshot of {{Product URL}}
Action 2: Gmail — Send Email — Attach file from Action 1

Daily website monitor → screenshot → Slack alert

Trigger: Schedule by Zapier — Every day at 9am
Action 1: Webhooks by Zapier — GET screenshot of your site
Action 2: Slack — Send message with file attachment

Authentication options

SnapSharp supports two authentication methods — both work in Zapier:

Option 1: Authorization header (recommended)

In the Headers field:

Authorization: Bearer sk_live_your_key_here

Option 2: X-API-Key header

X-API-Key: sk_live_your_key_here

Common parameters

Full parameter reference: snapsharp.dev/docs/screenshot

Handling errors

SnapSharp returns standard HTTP status codes:

• 200 — success, response body is the image
• 401 — wrong or missing API key
• 429 — rate limit or monthly quota exceeded
• 400 — invalid parameters (check query string values)

In Zapier, use Filters or Paths to handle error cases — for example, only proceed if the Webhooks step succeeded.

Rate limits

For high-volume Zaps, enable Overage Billing in your dashboard to avoid blocked requests.

Ready to start? Get your API key at snapsharp.dev/api-keys and build your first screenshot Zap in under 5 minutes.