How to Automate Screenshots with Make.com: A No-Code Visual Workflow Guide

Make.com (formerly Integromat) is a visual automation platform with a node-based workflow editor. Like Zapier, it connects hundreds of apps — but its HTTP module is more flexible than Zapier's Webhooks action, and its visual canvas makes multi-step workflows easier to read and debug.

This guide covers the core patterns for screenshot automation in Make.com, with no code required.

The Core Module: HTTP → Make a Request

Every screenshot workflow in Make.com uses one central module: HTTP → Make a Request.

To add it: 1. Click the + button on the canvas 2. Search for "HTTP" 3. Select HTTP → Make a Request

Configure it as follows:

Query string parameters to add: - url → the target webpage URL (or map from a previous module) - key → your Hermesforge API key - width → 1440 - format → png - full_page → true (optional)

The response will be binary image data, which Make.com handles as a file that can be passed to storage modules (Google Drive, Dropbox, etc.) or email attachments.

Pattern 1: Scheduled Screenshot to Google Drive

Capture a webpage screenshot on a schedule and save it to a dated folder in Google Drive.

Module 1: Schedule (trigger) - Set interval: daily, weekly, hourly - This fires your scenario on the chosen schedule

Module 2: HTTP → Make a Request - URL: https://hermesforge.dev/api/screenshot - Query: url=https://yoursite.com, key=YOUR_KEY, width=1440, format=png - Response type: Binary

Module 3: Google Drive → Upload a File - File name: use Make's date formatting — screenshot-{{formatDate(now; "YYYY-MM-DD")}}.png - File content: map the binary output from the HTTP module - Folder: select or create a "Screenshots" folder

Result: a dated screenshot file in Google Drive on every scheduled run.

Pattern 2: Google Sheets Row → Screenshot → Update Row

Process a list of URLs from a spreadsheet, screenshot each one, and write the result back.

Module 1: Google Sheets → Watch Rows - Watch for new rows in a target sheet - Map the URL column to a variable

Module 2: HTTP → Make a Request - Map the URL from the Sheets trigger to the url query parameter - url = {{1.URL}} (Make's variable notation for module 1's URL column)

Module 3: Google Drive → Upload a File - Save the screenshot - Copy the file's web view link from the output

Module 4: Google Sheets → Update a Row - Write the Drive link back to the same row (column B, or a "Screenshot" column)

This creates a self-updating spreadsheet: add URLs to column A, get screenshot links in column B automatically.

Pattern 3: Webhook Trigger → Screenshot → Slack

When an external system sends a webhook (a new deployment, a form submission, a content publish event), screenshot the relevant URL and post it to Slack.

Module 1: Webhooks → Custom Webhook - Make.com generates a unique webhook URL - Configure your external system to POST to that URL with a url field in the JSON body

Module 2: HTTP → Make a Request - url query param: {{1.url}} (mapped from the webhook body) - Screenshot the URL from the incoming webhook

Module 3: Slack → Upload a File - Channel: your target channel (e.g. #deploys, #design-review) - File: map the binary output from the HTTP module - Message: Screenshot of {{1.url}} captured at {{formatDate(now; "HH:mm")}}

Use cases: visual deploy verification (screenshot the live URL after each deployment), design review (screenshot submitted URLs for review), content audit (screenshot each published article URL).

Pattern 4: Iterator for Bulk Processing

Make.com's Iterator module processes a list of items one by one through the rest of the scenario. This is the right pattern for batch URL processing.

Module 1: Google Sheets → Get Rows (or any source of a URL list) - Get all rows from a spreadsheet

Module 2: Iterator - Takes the array of rows from module 1 - Passes each row individually to subsequent modules

Module 3: HTTP → Make a Request - url = {{2.URL}} (the URL column from each row, via the iterator)

Module 4: Google Drive → Upload a File - Save screenshot with filename based on the URL: {{replace(2.URL; "https://"; "")}}.png

Module 5: Google Sheets → Update a Row - Write screenshot link back to the row

The Iterator pattern is Make.com's equivalent of a for-loop: one HTTP request per row, processed in sequence.

Error Handling

Make.com has built-in error handling at the module level. For screenshot workflows:

Add an error handler to the HTTP module: - Right-click the HTTP module → Add error handler - Choose "Resume" to continue with the next item if one fails - Or "Break" to stop and notify

Common errors and fixes: - 429 (rate limit): add a sleep module before the HTTP call, or upgrade to Pro tier (1,000/day) - 400 (bad URL): add a filter before the HTTP module checking that the URL starts with http - Timeout: set HTTP module timeout to 30 seconds (screenshot of complex pages can take 10–20s)

Add a filter before the HTTP module: - Condition: URL contains http - This skips rows with empty or malformed URLs

Make.com vs Zapier for Screenshot Workflows

Make.com is better for complex multi-step workflows, bulk processing, and scenarios where you need per-module error handling. Zapier is faster to set up for simple linear workflows.

Complete Template: Competitor Monitoring Dashboard

Here's a full Make.com scenario structure:

1. Schedule (daily at 08:00)
2. Google Sheets → Get Rows (competitor URL list)
3. Iterator (process each row)
4. HTTP → Make a Request (screenshot each URL)
5. Google Drive → Upload File (save with date + domain in filename)
6. Google Sheets → Update Row (write Drive link back)
7. Gmail → Send Email (daily digest: "5 competitor screenshots captured — [Drive folder link]")

This scenario runs every morning, screenshots all competitors, saves to Drive, and emails you a link to the folder. No daily manual action required.

Hermesforge Screenshot API works in any Make.com workflow via the HTTP module. Get your free API key — 50 screenshots/day, no signup required.