How to Take Screenshots in Make.com (Integromat) Automations

You're using Make.com to automate your business. You connect apps, trigger workflows, capture data from web pages. But everything you capture is text or JSON. You never actually see what happened on the page.

What if you could add visual proof to your automations?

One HTTP module. One API call. Now your Make.com scenario captures screenshots.

Why Make.com + Screenshots

Make.com is powerful for connecting SaaS apps and automating business logic. But the web is visual. When your scenario navigates a page or extracts data, screenshots give you:

• Verification: Did the page actually load?
• Debugging: What went wrong if the automation failed?
• Compliance: Visual audit trail for regulated processes
• Monitoring: Screenshot page state at each workflow step

Setup: Add PageBolt to Your Make.com Scenario

Step 1: Add HTTP Module

In your Make.com scenario:

1. Click + to add a module
2. Search HTTP
3. Select HTTP → Make a request

Step 2: Configure the Request

Set these fields:

Field	Value
URL	https://api.pagebolt.dev/v1/screenshot
Method	POST
Headers	Add custom header

Step 3: Add Authorization Header

1. Click Headers
2. Add header:
   • Name: Authorization
   • Value: Bearer YOUR_PAGEBOLT_API_KEY
3. Add header:
   • Name: Content-Type
   • Value: application/json

Get your API key from pagebolt.dev/dashboard.

Step 4: Add Request Body

In the HTTP module:

1. Set Body type to Raw
2. In the Body field, add:

{
  "url": "https://example.com/page",
  "format": "png",
  "width": 1280,
  "height": 720
}

Use Make.com variables for dynamic URLs:

{
  "url": "{{ 1.url }}",
  "format": "png",
  "width": 1280,
  "height": 720
}

(Replace 1.url with your previous module's output field.)

Step 5: Handle Binary Response (Critical!)

This is the key difference in Make.com. The response is binary PNG data, not JSON.

In the HTTP module:

1. Go to Show advanced settings
2. Set Parse response to No

This tells Make.com: "Don't try to parse this as JSON. It's binary data."

Make.com will automatically create a data field containing the binary PNG. You can use this directly in the next modules.

Real Example: Daily Competitor Price Monitoring

Here's a complete Make.com scenario that screenshots a competitor's pricing page every morning and saves it to Google Drive:

Modules:

1. Schedule → "Every day at 9:00 AM"
2. HTTP (PageBolt) → Screenshot competitor pricing
3. Google Drive → Upload screenshot to Drive
4. Slack → Send notification with screenshot

Configuration:

Module 1 - Schedule:

• Trigger type: "Scheduler"
• Time: "09:00" (9 AM)
• Repeat: "Every day"

Module 2 - HTTP (PageBolt):

URL: https://api.pagebolt.dev/v1/screenshot
Method: POST

Headers:
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Body (JSON):
{
  "url": "https://competitor.com/pricing",
  "format": "png",
  "fullPage": true,
  "blockBanners": true
}

Show advanced settings:
Parse response: No

Module 3 - Google Drive → Upload file:

• File content: 2.data (binary PNG from HTTP module)
• File name: competitor-pricing-{{ now }}.png
• Folder: "Screenshots" folder in Google Drive

Module 4 - Slack → Send message:

• Channel: #monitoring
• Message: Daily competitor price check complete. See file.

Now every morning at 9 AM, the scenario:

1. Screenshots competitor pricing
2. Uploads to Google Drive with timestamp
3. Notifies Slack

You have a dated history of competitor pricing. Spot changes immediately.

Use Case: Form Submission Capture

After a form is submitted, screenshot the confirmation page:

{
  "url": "{{ 3.confirmationUrl }}",
  "format": "png",
  "blockBanners": true,
  "blockAds": true
}

Store with order metadata:

Module: Google Drive → Upload file

• File content: 4.data
• File name: order-{{ 1.orderId }}-confirmation.png
• Folder: "Submissions/{{ now.year }}/{{ now.month }}"

Now you have visual proof of every form submission.

Use Case: Visual Audit Trail

Log what a page looked like at each step of a business process:

Scenario: Lead Qualification Flow

1. Get lead details
2. Visit lead's LinkedIn → Screenshot
3. Check email reputation → Screenshot
4. Archive both screenshots → Database

Pass screenshots to a database:

{
  "lead_id": "{{ 1.leadId }}",
  "timestamp": "{{ now }}",
  "step": "linkedin_check",
  "screenshot": "{{ 3.data }}",
  "screenshot_url": "s3://audit-bucket/{{ 1.leadId }}-linkedin.png"
}

Common PageBolt Parameters

Parameter	Example	Purpose
url	https://example.com	Page to screenshot
format	png	Always PNG
width	1280	Viewport width
height	720	Viewport height
fullPage	true	Capture entire page (including lazy-loaded content)
blockBanners	true	Hide cookie consent popups
blockAds	true	Remove advertisements
viewportDevice	iphone_14_pro	Mobile emulation

Error Handling in Make.com

Add error handling for failed screenshots:

1. After the HTTP module, add Router
2. Set condition: {{ 2.status }} = 200
3. Route success → Upload to Drive
4. Route failure → Send error notification to Slack

Storing Screenshots in Make.com

Option 1: Google Drive (easiest)

Use Google Drive → Upload file module:

• File content: {{ 2.data }}
• File name: screenshot-{{ now }}.png
• Folder: Designated Drive folder

Option 2: AWS S3 (scalable)

Use AWS S3 → Create/Update object module:

• Access Key: Your AWS access key
• Secret Key: Your AWS secret key
• Bucket: Your S3 bucket
• Key (path): screenshots/{{ now.ISO }}.png
• Content type: image/png
• File content: {{ 2.data }}

Option 3: Dropbox (team-friendly)

Use Dropbox → Create a file module:

• File content: {{ 2.data }}
• File name: screenshot-{{ now }}.png
• Folder path: /Screenshots/

Scenario Templates

Template 1: Daily Website Monitoring

Schedule (daily)
  ↓
Loop through URLs
  ↓
HTTP (PageBolt screenshot)
  ↓
Compare with previous day's screenshot
  ↓
If changed: Alert team, archive both screenshots

Template 2: Form Automation with Proof

Webhook (form submission)
  ↓
Extract form data
  ↓
Screenshot confirmation page
  ↓
Upload to Drive
  ↓
Update database
  ↓
Send confirmation email

Template 3: Price Monitoring Pipeline

Schedule (every hour)
  ↓
Loop through 10 competitor URLs
  ↓
Screenshot each
  ↓
Upload to S3 with timestamp
  ↓
Extract prices with OCR (optional)
  ↓
Alert if price changed

Pricing

Plan	Requests/Month	Cost	Best For
Free	100	$0	Testing scenarios
Starter	5,000	$29	Small monitoring
Growth	25,000	$79	Production scenarios
Scale	100,000	$199	Enterprise automation

Summary

Screenshots in Make.com automations:

• ✅ Add HTTP module calling PageBolt API
• ✅ Set "Parse response" to "No" for binary data
• ✅ Store to Google Drive, S3, or Dropbox
• ✅ Use in monitoring, verification, audit trails
• ✅ 100+ requests/month free

Get started: Try PageBolt free — 100 requests/month, no credit card →