SnapSharp + Make

Make (formerly Integromat) is a visual automation platform that competes directly with Zapier and trades per-task pricing for cheaper per-operation pricing — much friendlier at scale. SnapSharp's official Make integration exposes screenshot, OG image, HTML-to-image, PDF export, metadata extract, and site audit as drag-and-drop modules. Map fields visually, branch on success/failure with native error handlers, and build scenarios that fire every minute without burning through a quota. The integration is open-source under `packages/integration-make` in our monorepo, so you can inspect the manifest, contribute new modules, or fork it for private Make instances.

How it works

A typical end-to-end flow takes 1–3 seconds.

1. 1

   Add SnapSharp to a scenario

   Search for "SnapSharp" inside the Make module picker; pick the operation you need (Screenshot, OG, PDF, ...).

2. 2

   Authenticate via API key

   Make stores the SnapSharp API key in its built-in connection vault — paste it once, reuse everywhere.

3. 3

   Map upstream fields visually

   Drag any output of the previous module into SnapSharp's URL, width, template, or variables fields.

4. 4

   Route the result

   SnapSharp returns the binary, hosted URL, and metadata — pipe to Cloud Storage, Slack, Notion, or back into a sheet.

Setup guide

Follow these steps in order. Each one stands alone, so you can copy code blocks directly without re-reading earlier ones.

1. 1Open Make and create a scenario

   Sign in at make.com, click "Create a new scenario". Make scenarios are ordered from left to right; the first module is your trigger.

2. 2Pick a trigger

   Use any built-in Make trigger — Schedule, Webhook, Google Sheets row added, RSS new item, etc. The trigger output must include at least one URL, HTML string, or template payload.

3. 3Add the SnapSharp module

   Click the plus icon, search "SnapSharp", and pick the operation. On first use Make asks for a connection; paste your API key from the SnapSharp dashboard.

   // Connection vault stores:
   {
     "name": "SnapSharp Production",
     "apiKey": "ss_live_xxxxxxxxxxxx"
   }
   

4. 4Map fields with the visual editor

   Click each input on the SnapSharp module and drag tokens from upstream modules. Make supports IML expressions for transformations (`{{lower(1.url)}}`, `{{formatDate(now; 'YYYY-MM-DD')}}`).

5. 5Add a router for success/failure paths

   SnapSharp returns `success: true|false`. Wire the success path into Slack/Drive/Notion and the failure path into an alerting module. Make's native error handlers make this trivial.

6. 6Schedule the scenario

   Open scenario settings → Scheduling. Make supports cron-style intervals down to every 1 minute on paid plans, every 15 minutes on free.

Trigger examples

Real-world patterns where Make fires and SnapSharp produces the asset.

Action examples

Each card shows the operation and the inputs you'd typically map from upstream.

url: {{1.url}}
width: 1280
full_page: true
block_ads: true

template_id: launch-card
variables.title: {{1.headline}}
variables.cta: {{1.cta}}

html: {{1.html_body}}
width: 1080
format: png

url: {{1.invoice_url}}

url: {{1.url}}

Limitations to know

• •Make's polling triggers run on a configurable schedule; instant triggers (webhooks) are recommended for true real-time.
• •Operations consumed in Make are independent of SnapSharp's request quota — both meters run in parallel, so plan capacity on both sides.
• •Some niche SnapSharp parameters (custom JS injection, residential proxy country) are exposed via the "advanced JSON" field rather than dedicated UI inputs.

How SnapSharp compares to other apps in Make

Quick reference — every alternative listed below is also available in Make.

FAQ