How to Automate Screenshots with Make (Integromat)

Make (formerly Integromat) is one of the most powerful no-code automation platforms. Its HTTP → Make a Request module can call any REST API — including SnapSharp — and pass the binary image output to hundreds of other apps.

This guide covers exact module configuration, authentication, and real scenario examples you can use immediately.

What you need

• A SnapSharp account (free tier: 100 screenshots/month)
• Your API key from Dashboard → API Keys
• A Make account (free plan includes 1,000 operations/month)

Step 1: Add the HTTP module

In your Make scenario, click + to add a module:

1. Search for HTTP
2. Choose Make a Request

Step 2: Configure the module

Screenshot a URL (GET request)

Query String (click Add item for each):

Headers (click Add item):

Set Parse response to No — this tells Make to keep the response as a binary file, not try to parse it as JSON.

OG Image generation (POST request)

Request content:

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

Headers:

HTML to Image (POST request)

Render custom HTML/CSS as an image — useful for dynamic cards, receipts, reports:

Request content:

{
  "html": "<div style='background:#fff;padding:40px;font-family:sans-serif'><h1>{{title}}</h1><p>{{description}}</p></div>",
  "width": 1200,
  "height": 630,
  "format": "png"
}

Step 3: Use the image output

The HTTP module returns the image as a binary data bundle. Connect it to:

• Google Drive → Upload a File — pass the Data from the HTTP module as file content
• Dropbox → Upload a File
• Airtable → Create/Update a Record — attach to an attachment field
• Notion → Create a Page — embed the image
• Gmail → Send an Email — attach to email
• Slack → Upload a File — post to a channel
• AWS S3 → Upload an Object

In most storage modules, look for a File or Data field and map it to the HTTP module's output data.

Real scenario examples

Webflow CMS item published → screenshot → store in Airtable

Trigger: Webflow → Watch Items (new item published)
  ↓
HTTP: GET https://api.snapsharp.dev/v1/screenshot
  url={{item.slug URL}}
  width=1280, format=png
  ↓
Airtable: Update Record
  Attachments field ← HTTP module data

Google Sheets row added → site audit → parse results → update sheet

Trigger: Google Sheets → Watch New Rows
  ↓
HTTP: GET https://api.snapsharp.dev/v1/site-audit
  url={{sheet row URL}}
  (Parse response: YES — returns JSON)
  ↓
Google Sheets: Update Row
  Colors column ← audit.colors
  Tech stack column ← audit.technologies

For /v1/site-audit and /v1/usage, set Parse response to Yes — these endpoints return JSON, not binary.

Scheduled daily screenshot → compare → Slack alert

Trigger: Make → Schedule (every day 9:00 AM)
  ↓
HTTP: GET /v1/screenshot?url=https://yoursite.com
  ↓
Google Drive: Upload file (overwrite previous)
  ↓
Slack: Send message "Daily screenshot captured"

Airtable product URLs → batch screenshots → attach to records

Use the Iterator module to loop through rows:

Trigger: Airtable → Search Records (all products)
  ↓
Iterator → loop over each record
  ↓
HTTP: GET /v1/screenshot?url={{product.URL}}
  ↓
Airtable: Update Record → attach screenshot

Authentication

Make supports two approaches:

Option 1: Header auth (recommended)

In the HTTP module → Headers:

Name:  Authorization
Value: Bearer sk_live_your_key_here

Option 2: Stored credentials via Make's HTTP Basic Auth

In the HTTP module → Show advanced settings → Authentication → Basic Auth:

• Login: api
• Password: YOUR_API_KEY

Both work — headers approach is more explicit and easier to debug.

Common parameters

Error handling in Make

Use the Error Handler route in Make to handle failures gracefully:

1. Right-click on the HTTP module → Add error handler
2. Choose Resume or Ignore depending on the scenario
3. Add a Slack or Email notification for 4xx/5xx responses

Common HTTP status codes from SnapSharp:

Rate limits

For high-volume scenarios with many iterations, add a Sleep module (1–2 seconds) between HTTP calls to stay within per-minute limits.

Ready to build? Get your API key at snapsharp.dev/api-keys and create your first Make scenario in under 5 minutes.

Related: Integrations docs · Pricing · Automate Screenshots with Zapier