Automating Screenshots with Make (Integromat): A No-Code Recipe

Make (formerly Integromat) is a common choice for teams that want visual automation but do not want to write or maintain a script. Like Zapier, Make has no dedicated Snapshot Site app in its directory — but that is not a blocker. Its generic HTTP module can call any REST API directly, which is all a screenshot request really is.

This walks through one concrete scenario: a new row in a Google Sheet triggers a capture, and the result lands in Slack.

What This Scenario Does

1. Trigger: a new row is added to a Google Sheet (a url column anyone on the team can fill in).
2. Action 1: Make's HTTP module sends a POST request to the Snapshot Site API with that URL.
3. Action 2: the screenshot link from the response is posted to a Slack channel.

Step 1: Trigger on a New Google Sheets Row

Create a scenario in Make with Google Sheets → Watch Rows as the trigger module, pointed at a sheet with a url column. This is the intake point — no one needs API access to add a page to the queue.

Step 2: Call Snapshot Site with the HTTP Module

Add Make's HTTP → Make a request module:

• URL: https://api.prod.ss.snapshot-site.com/api/v1/screenshot
• Method: POST
• Body type: Raw / JSON (application/json)
• Request content:

{
  "url": "{{1.url}}",
  "format": "png",
  "width": 1440,
  "height": 900,
  "fullSize": true,
  "hideCookie": true
}

• Headers:
  • Content-Type: application/json
  • x-snapshotsiteapi-key: your Snapshot Site API key

{{1.url}} maps to the url column from the Google Sheets trigger — Make's mapping panel picks this up automatically once the trigger module runs once.

Step 3: Post the Result to Slack

Add a Slack → Create a Message module. The HTTP module's output includes the screenshot URL in its response body — reference {{2.data.link}} (or whichever path matches the actual response field) in the Slack message text, alongside the original page URL from Step 1, so the channel shows both the source and the result.

Why the Generic HTTP Module Is the Right Call

A purpose-built app in Make's directory would only expose whatever fields its maintainer wired up. The HTTP module exposes every parameter the API supports — delay, hide, format, fullSize, and the rest — in the same request body shown throughout the API docs. That means the no-code version of this workflow is never behind what a script could do; it is the same request, filled in through a form instead of code.

Extending the Scenario

Once this base scenario works, the same HTTP module pattern extends naturally:

• Swap the trigger for a schedule to capture a fixed list of pages on a recurring basis.
• Add a second HTTP module calling /api/v3/compare to diff the new capture against a stored baseline.
• Route the result into Notion or Airtable instead of Slack for a running visual log.

If your team is comparing Make against other automation tools for this kind of workflow, Sending Snapshot Site Screenshots to Slack and Google Sheets with Zapier walks through the equivalent Zapier setup side by side.

Snapshot Site works the same way regardless of which automation platform is making the call — the API does not know or care whether the request came from a script, a CI job, or a no-code HTTP module.