ZapierBeta

Screenshot API for Zapier

Screenshots by Snapshot Site puts website capture, pixel-level visual comparison, and AI page analysis inside your Zaps. Point a step at a URL and pass the result to Slack, Google Sheets, Notion, or any of the other apps Zapier connects to.

1 trigger
Website Changed, polling
3 actions
Capture, analyze, compare
API key
One field to connect
Status
Beta

The app is published on Zapier and usable today, but it is still listed as Beta: it does not appear in Zapier's public app directory search, so you connect it from the integration page linked below. Expect the trigger and action fields to still change.

What the app exposes

Four steps, each mapped to a single Snapshot Site endpoint. Nothing is proxied through an intermediate service.

StepNameEndpointWhat it does
TriggerWebsite Changed/api/v2/screenshot + /api/v3/compareCaptures the URL on each poll, compares it against the capture from the previous poll, and fires only when the visual change clears your threshold.
ActionCapture ScreenshotPOST /api/v2/screenshotScreenshots a page as PNG, JPEG, WebP, PDF, base64, or raw HTML, with viewport, full-page, and cookie-banner controls.
ActionAnalyze PagePOST /api/v3/analyzeReturns an AI summary, topics, a heading outline, SEO metadata, and quality checks such as blank-page and CAPTCHA detection.
ActionCompare PagesPOST /api/v3/compareRuns a pixel-level diff between two pages, or between a live page and a stored baseline image, and returns a mismatch score plus a diff image.
Quick start

From an empty Zap to a first capture

  1. 1

    Create an API key in the Snapshot Site console, on the API keys page.

  2. 2

    Open the Screenshots by Snapshot Site page on Zapier — the link is at the top of this page — and start a Zap with it.

  3. 3

    Add a Snapshot Site connection and paste your API key. It is the only field — the API endpoint is fixed.

  4. 4

    Pick your step: Website Changed as a trigger, or Capture Screenshot, Analyze Page, or Compare Pages as an action.

  5. 5

    Map the URL field from your trigger data, then send the returned file or JSON on to Slack, Google Sheets, Notion, or Drive.

  6. 6

    Test the step. Connecting runs a real capture of example.com, so an invalid key fails immediately with a 401 rather than at the first live run.

Limits worth knowing before you build

The app is in Beta

It works, and it is the official app, but it is not GA. Field names and defaults can still change between releases, which may require reopening a Zap after an update.

Website Changed polls, it does not receive webhooks

The Snapshot Site API is synchronous and stateless, so there is nothing to push a callback. Zapier schedules the check on your plan's polling interval, which sets the floor on how fast you can detect a change.

The first check never fires

A new Zap has no previous capture to diff against, so the first poll only stores a baseline. This is expected — the trigger starts firing from the second poll onward.

Sensitivity needs tuning per page

Minimum Change (%) gates on the share of pixels that moved and Pixel Sensitivity (0–1) sets the per-pixel colour tolerance. Pages with carousels, ads, or timestamps need both raised, or every poll reads as a change.

Captures count against your plan

A Zap step is a normal API call. The Website Changed trigger spends one capture per poll, whether or not it fires — worth doing the arithmetic before pointing it at a short interval.

Zapier integration FAQ

Do I need to write any code to use Snapshot Site in Zapier?

No. The app exposes the screenshot, analyze, and compare endpoints as regular Zapier steps with form fields. You only need an API key from your Snapshot Site account.

Why doesn't my Website Changed trigger fire on the first run?

The first poll has no earlier capture to compare against, so it stores one as the baseline and stops there. From the second poll on, each run diffs against the previous capture and fires when the change clears your threshold.

Can I get an alert faster than my Zapier polling interval?

Not through the trigger — the detection speed is bounded by how often Zapier runs the poll on your plan. If you need tighter intervals, drive the compare endpoint on your own schedule with the API, the CLI, or an n8n workflow.

Is the Zapier app production-ready?

It is published and functional, but still marked Beta, so field shapes may change between releases. If you need a frozen contract today, call the API directly or use one of the official SDKs.

How many captures does a monitoring Zap consume?

One capture per poll for the Website Changed trigger, plus one per action step you run. A Zap polling every 15 minutes spends roughly 2,880 captures a month, so size your plan against your interval.

Build your first screenshot Zap

Create an API key, connect the app, and wire a capture into the workflow you already run. The free plan includes 50 captures per month.