Sending Snapshot Site Screenshots to Slack and Google Sheets with Zapier

Not every team wants to write and maintain a script for something as simple as "capture this page and post it to Slack." If your team already lives in Zapier, you can wire that up as a single Zap without touching code, using Zapier's generic Webhooks action to call the Snapshot Site API directly.

This walks through one concrete Zap end to end: a new row in a Google Sheet triggers a screenshot, and the result gets posted to both Slack and back into the sheet.

What This Zap Does

1. Trigger: a new row is added to a Google Sheet (e.g. a marketing team drops in a campaign landing page URL).
2. Action 1: Zapier's "Webhooks by Zapier" app sends a POST request to the Snapshot Site API with that URL.
3. Action 2: the screenshot link from the response gets posted to a Slack channel.
4. Action 3: the same link gets written back into the sheet, next to the original row.

Step 1: Trigger on a New Google Sheets Row

In Zapier, create a new Zap with Google Sheets → New Spreadsheet Row as the trigger, pointed at a sheet with at least a url column. This is where anyone on the team can drop in a page to capture, without needing API access themselves.

Step 2: Call Snapshot Site with Webhooks by Zapier

Add an action step using the Webhooks by Zapier app, action type POST:

• URL: https://api.prod.ss.snapshot-site.com/api/v1/screenshot
• Payload Type: json
• Data:
  • url: map this to the url column from the trigger row
  • format: png
  • width: 1440
  • height: 900
  • fullSize: true
  • hideCookie: true
• Headers:
  • Content-Type: application/json
  • x-snapshotsiteapi-key: your Snapshot Site API key

Since there is no dedicated Snapshot Site app in the Zapier directory, "Webhooks by Zapier" is the action that does the job — it is a plain authenticated HTTP call, the same request shape shown throughout the API docs.

Step 3: Post the Result to Slack

Add a Slack → Send Channel Message action. The webhook response includes the screenshot URL — reference that field directly in the Slack message body, along with the original page URL from the trigger step, so the channel sees both what was captured and where it came from.

Step 4: Write the Link Back to the Sheet

Add a Google Sheets → Update Spreadsheet Row action, writing the screenshot URL from Step 2 into a screenshot column on the same row that triggered the Zap. Now the sheet doubles as a running log: every URL a teammate drops in gets a screenshot next to it, with no one needing to run anything manually.

Where to Take This Further

This one Zap covers a single, concrete recipe. If you want more patterns — routing into Notion galleries, Airtable proofing boards, or Make/n8n instead of Zapier — see No-Code Screenshot Automation Recipes with Snapshot Site for a broader tour of the no-code side of the API.

The advantage of routing through a generic webhook action rather than a purpose-built integration is that any parameter the API supports — delay, hideCookie, format, and the rest — is available in the same Zap step, so the automation is never behind what the API itself can do. Snapshot Site works the same whether the request comes from a script, a CI job, or a no-code webhook step like this one.