Screenshots by Snapshot Site is Now Available on Zapier

The official Screenshots by Snapshot Site integration is now available on Zapier. It brings website capture, visual comparison, rendered-page analysis, and change detection into the same visual workflow builder teams already use for Slack, Google Sheets, Notion, email, storage, and thousands of other apps.

You no longer need to assemble the basic request with a generic webhook. Connect your Snapshot Site account, choose a trigger or action, map the URL from an earlier Zap step, and route the result into the next app.

Open Screenshots by Snapshot Site on Zapier or create a Snapshot Site account before building your first Zap.

What the Zapier integration includes

The integration exposes one trigger and three actions:

These events map to the same core operations documented in the Screenshot API, Visual Diff API, and AI website analysis pages. Zapier provides the orchestration layer: another app supplies the URL, Snapshot Site processes the page, and a later step decides where the evidence or structured result should go.

1. Capture screenshots without an HTTP step

Use Capture Screenshot when a Zap already has a page URL and needs a visual asset. Common triggers include a new CMS item, a Google Sheets row, a form submission, a deployment event, or a scheduled review.

The action supports:

• hosted PNG, JPEG, WebP, or PDF output;
• base64 image output;
• rendered HTML;
• viewport width and height;
• full-page capture;
• a post-load delay;
• cookie-banner hiding;
• CSS selectors to hide;
• custom JavaScript before capture;
• language and country settings.

A straightforward workflow looks like this:

1. Trigger: a new campaign URL is added to a Google Sheet.
2. Action: Capture Screenshot renders the full landing page as PNG.
3. Action: Slack posts the page URL and hosted screenshot link to a review channel.
4. Action: Google Sheets stores that link beside the source URL.

If you previously built this flow with Webhooks by Zapier, the dedicated action removes the manual endpoint, header, and JSON configuration. The existing Slack and Google Sheets walkthrough remains useful for the routing pattern; replace its webhook step with Capture Screenshot.

2. Trigger a Zap when a website changes visually

Website Changed turns visual monitoring into a Zap trigger. On each check, the integration captures the configured URL, compares it with the previous capture, and emits an event when the mismatch reaches your minimum change percentage.

The first check behaves differently by design: it creates the initial baseline and does not trigger the downstream steps. The next check has two page states to compare.

Configure two separate controls carefully:

• Minimum Change (%) decides how much of the page must change before the Zap fires.
• Pixel Sensitivity controls how different individual pixel colors must be before they count as changed.

Start with a stable viewport and hide known volatile regions such as timestamps, rotating banners, or live counters. Otherwise, harmless motion can generate noisy alerts. The website monitoring guide explains how to choose representative pages and maintain useful baselines.

A practical monitoring Zap can be as small as:

1. Trigger: Website Changed monitors a pricing or product page.
2. Filter: continue only when the mismatch is above the team’s review threshold.
3. Action: send the before, after, and diff links to Slack.
4. Action: append the timestamp and mismatch percentage to an audit sheet.

The trigger performs screenshot work whenever Zapier polls it, even when no change event is emitted. Choose the number of monitored URLs and your Snapshot Site plan with that recurring usage in mind. Review pricing before activating a large monitoring set.

3. Compare pages inside any Zap

Use Compare Pages when another event should initiate the check rather than the integration’s polling trigger. For example, run a comparison after a deployment, when a QA ticket changes status, or when a content editor publishes a page.

Each side can be:

• a live URL with its own viewport and rendering options; or
• an existing image URL used as a fixed reference.

Read the full article on Snapshot Site →