Snapy and Make

What this does

Make (formerly Integromat) runs visual automations. With the HTTP module, a scenario can send content to Snapy, get a link back, and pass that link to any later module. The Snapy publish endpoint is open and free, so no Snapy module, key, or login is needed. The HTTP module does the whole job.

How to set it up

1. Add an HTTP module and pick Make a request.
2. Method: POST.
3. URL: https://api.snapy.host/api/publish.
4. Body type: Raw, content type application/json, with: { "content": "{{your_html}}", "name": "optional-name", "filename": "index.html" }
5. Turn on Parse response so Make reads the JSON.

After it runs, the url from the response is available to map into the next module, like sending the link by email or posting it to a channel. The response also includes stats_url (a private analytics page) and token (for managing the link). Leave name out for a random address.

Example workflow

A clear pattern is new file in Google Drive, publish to Snapy, post link to Slack:

1. Google Drive: Watch Files in a chosen folder triggers the scenario.
2. HTTP: Make a request POSTs to https://api.snapy.host/api/publish. Map the file text into content. For a binary file like a PDF, run it through a base64 step first and send it as content_base64 with a filename.
3. Slack: Create a Message uses the parsed url from the HTTP module in the message text.

Each new file in the folder becomes a live link in your channel with no manual step.

Other scenarios that follow the same shape:

• A scheduled scenario builds a daily report as HTML, publishes it to Snapy, and posts the fresh link to your team chat every morning.
• A new Airtable record becomes a hosted summary page whose link is written back to the record.
• An incoming webhook turns a payload into a page and emails the link onward.

Common uses

• Publishing reports, summaries, and dashboards as links on a schedule.
• Sharing files from cloud storage as clean URLs.
• Turning form and database records into hosted pages.
• Sending a link instead of an attachment in automated emails.

Snapy serves static files. Self-contained HTML and documents work well. Anything that needs a live server or database is out of scope.

Troubleshooting

• No url in the parsed output. Turn on Parse response in the HTTP module. Without it, Make keeps the body as raw text and the url field is not mappable.
• Body sent wrong. Use Body type Raw with content type application/json, and make sure the JSON is valid after your variables are filled in.
• Binary file is broken. Do not put a PDF or image into content. Base64 encode it and send content_base64 with a matching filename.
• Name already taken. Choose a different name, or omit it for a random address.

Using the link downstream

Once Parse response is on, the HTTP module exposes the url, stats_url, and token fields as mappable items. Map url into whatever comes next: a Slack message, an email body, a new database record, or a reply in a webhook response. Map stats_url if you want the private analytics page recorded somewhere, and store token if a later automation needs to manage the link. To keep a stable address across runs, pass the same name each time so the scenario always publishes to a predictable URL.

Common patterns

• On a schedule: a daily or hourly scenario builds content, publishes it, and pushes the link to a channel.
• On a trigger: a new file, form entry, or record fires the scenario, which publishes and shares the link.
• As a sub-step: an existing scenario adds an HTTP module mid-flow to turn generated HTML into a link before continuing.

Each pattern reuses the same single HTTP module, so adding Snapy to a working scenario is a small change rather than a rebuild.

Good to know

• Free, no account, no API key.
• The same approach works in Zapier and n8n, and you can browse all integrations.

See the developer docs for all the fields. One HTTP module turns any scenario output into a link.