Make (Integromat) Integration
Build visual automation workflows with Make (formerly Integromat) using the HTTP module. Create complex screenshot pipelines with drag-and-drop — schedule captures, route results to multiple destinations, and chain screenshot operations with data transformation steps.
Quick Start
Set up your account
Sign up for Make (formerly Integromat) at make.com and create a new scenario with an HTTP module.
Add HTTP module
Add an HTTP request module to make API calls.
Configure the request
Set up the POST request with Screenshotly API endpoint and authentication.
Connect your apps
Link the screenshot output to your destination apps.
Setup Steps
Create a new scenario in Make
Add an HTTP module and select "Make a request"
Configure the POST request to Screenshotly API
Set up authentication with your API key
Add downstream modules to process screenshots
Schedule or trigger your scenario
When to Use Make (Integromat) with Screenshotly
Use the Make integration for complex, multi-step visual automation workflows with branching logic. Make is ideal when you need to route screenshots to multiple destinations, apply conditional processing, or chain screenshot captures with data transformation steps.
Make (Integromat) Best Practices
Use Make's built-in 'Parse JSON' module after the HTTP response to extract status codes and error messages before routing.
Set the HTTP module's 'Parse response' toggle to 'No' when receiving binary image data — raw mode avoids encoding issues.
Use Make's Router module to send screenshots to multiple destinations in parallel (e.g., Google Drive AND Slack).
Set up error handlers on the HTTP module to automatically retry on 429 (rate limit) responses with a configurable delay.
Make (Integromat): Production Notes
Make's pricing (operations per month, not tasks) is fundamentally more favorable for screenshot workflows. A typical capture scenario runs 3–5 operations, and Make's $9/month plan includes 10,000 operations — 2–3k captures for $9 vs. Zapier's $74 for equivalent volume.
Make's HTTP module supports request streaming and binary data natively, which Zapier struggles with. For capture-and-upload flows (S3, Drive, Dropbox with custom metadata), Make handles the binary pipe cleanly. For multi-MB PDFs, watch Make's 10 MB per-operation ceiling.
The best-fit Make pattern: Iterator fed a URL list, Router branching on capture success/failure, Aggregator collecting results into a summary notification. Replaces 20 lines of code with a visual scenario a non-developer can maintain.
Error Handling Recipes
Concrete strategies for each failure mode. Do not silently swallow errors — surface them to your monitoring so the pipeline is observable.
HTTP 429
Use a Sleep module with duration from Retry-After, then route back to the HTTP module. Make supports this loop natively.
Scenario timeout
Default scenario timeout is 40 minutes. For batch runs over 1,000 URLs, split into multiple scheduled runs with an offset filter.
Binary response on HTTP module
Set "Parse response" to No and pass binary directly to the destination module (Drive, Dropbox, HTTP upload). Trying to parse as JSON breaks.
Production Hardening Checklist
The difference between dev code and prod code. Work through these before putting Make (Integromat) captures on a critical path.
- API key stored as a Make Connection, not in plaintext module config.
- HTTP module parse-response set to No for binary image data.
- Error handler routes auth errors away from retry loops.
- Scenario scheduling respects Make operation quota.
- Failure notifications route to email or Slack via dedicated error-handler branch.
- Scenarios documented with description field: trigger, destination, owner.
Rate-Limit Strategy
Make's HTTP module supports explicit rate limiting in the module settings — set max requests per second to 1–2 to stay well below Screenshotly's QPS. For iterated scenarios, pair the Iterator with a Sleep module to throttle.
When Make (Integromat) isn't the right fit
Make (Integromat) works well for most capture workloads, but these patterns are legitimate reasons to pick a different stack:
- Your workflow requires custom code logic beyond what Make's Tools and Code modules handle. At that complexity, a real codebase with proper version control is easier to maintain.
- You need data residency or air-gapped deployment. Make is cloud-only — n8n self-hosted is the right answer when data cannot leave your infrastructure.
- Your team is deeply Zapier-skilled and retooling costs exceed the per-operation savings. Staying on Zapier is fine if volume is low.
Want a step-by-step walkthrough?
Read the full Make (Integromat) tutorial →API Reference
POST /api/screenshotBearer tokenapplication/jsonFrequently Asked Questions
How do I set up Screenshotly in Make (Integromat)?
Add an HTTP module to your scenario, select 'Make a request', set the method to POST, enter https://api.screenshotly.app/screenshot as the URL, add your API key in the Authorization header as 'Bearer YOUR_KEY', and configure the JSON body with your screenshot options.
Can I process screenshots with other Make modules?
Yes. After the HTTP module captures the screenshot, you can pipe the output to Google Drive, Dropbox, AWS S3, Airtable, or any of Make's 1,500+ integrations. Use the binary data from the response to upload or attach files.
How do I schedule recurring screenshot captures in Make?
Set your scenario's trigger to 'Scheduled' and choose a frequency (every 15 minutes, hourly, daily, etc.). Make will run the scenario automatically and capture fresh screenshots at each interval.
What's the difference between using Make vs Zapier for screenshots?
Make offers more complex branching logic, better error handling, and visual flow design. It's better for multi-step scenarios where you need to process, resize, or route screenshots conditionally. Zapier is simpler for straightforward A-to-B workflows.
Start building with Make (Integromat)
Get your API key and start capturing screenshots in minutes.
Other Platforms
Zapier
Connect Screenshotly with 5,000+ apps through Zapier using the Webhooks action. Automate screenshot workflows without writing code — capture pages when Google Sheets rows are added, save screenshots to Drive on form submissions, or post visual updates to Slack on a schedule.
n8n
Self-hosted workflow automation with n8n for teams that need full control over their data. Use the HTTP Request node to call the Screenshotly API, schedule recurring captures, and store results in your own infrastructure. Ideal for privacy-sensitive environments and air-gapped networks.