In Make (formerly Integromat), add an HTTP → Make a request module wherever your scenario needs a capture. The JSON response's url field becomes a mappable item for every downstream module — Google Drive, Slack, Notion, email.
For file workflows, choose 'Make a request' with response parsing off and map the binary body into a file-accepting module instead.
HTTP module configuration
// Module: HTTP → Make a request// Method: POST// URL: https://api.screenshotty.link/api/v1/screenshot// Headers:// X-Api-Key: (your key — store via Make's connection/keychain)// Content-Type: application/json// Body type: Raw (JSON){"url": "{{1.pageUrl}}","full_page": true,"block_cookie_banner": true,"response_type": "json"}// Parse response: Yes → use {{2.url}} downstream
Everything You Need, Built In
Plain HTTP module
No custom app required — works on every Make plan with the standard HTTP module.
Mappable output
JSON mode exposes the screenshot URL as a normal mappable field in the scenario flow.
Scenario scheduling
Make's built-in scheduling turns one module into recurring visual monitoring.
PDF support
Switch format to application/pdf to archive pages into Drive or Dropbox.
Frequently Asked Questions
How do I upload the capture to Google Drive?
Either pass the hosted URL to an HTTP Get a file module and feed its binary into Drive's Upload a file, or call the API with binary response and map the body directly.
Can one scenario capture multiple URLs?
Yes — use an Iterator over your URL list feeding the HTTP module; Make runs one capture per bundle.
Where do I get an API key?
Sign up at screenshotty.link (free tier: 100 screenshots/month, no credit card) and copy your key from the dashboard. Keep it in the integration's credential store rather than pasting it into shared workflows.
Does this count against Make operations?
Each capture is one HTTP operation in Make plus one Screenshotty request — both sides stay predictable and visible in their respective dashboards.