Snapy and Zapier

What this does

Zapier lets you connect apps without code. Using a Webhooks step, a Zap can send content to Snapy, get a link back, and use that link in later steps, like posting it to Slack, a sheet, or an email. The Snapy publish endpoint is open and free, so there is no app to install and no key to manage. You point a POST at one URL and read the url it returns.

How to set it up

1. In your Zap, add an action step and choose Webhooks by Zapier.
2. Pick the POST event.
3. Set the URL to https://api.snapy.host/api/publish.
4. Set payload type to JSON and add these fields: - content = the text or HTML you want to publish (map it from an earlier step) - name = an optional link name (leave blank for a random address) - filename = optional, such as index.html
5. Make sure the Unflatten option is left at its default so the JSON is sent cleanly.
6. Turn the step on.

The step returns a url. Zapier also surfaces stats_url (your private analytics page) and token. In the next action, map the url value wherever you want the link, for example into a Slack message, a Gmail body, or a new sheet row.

Example workflow

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

1. Trigger: Google Drive, New File in Folder.
2. Action: Webhooks by Zapier, POST to https://api.snapy.host/api/publish. Map the file's text content into content. (For a binary file like a PDF, base64 encode the file first and send it as content_base64 with a filename.)
3. Action: Slack, Send Channel Message. In the message text, insert the url returned by the webhook step.

Now every new file in that folder turns into a live link that lands in your team channel automatically.

Other examples that work the same way:

• A new form entry becomes a hosted summary page, and the link is emailed to the submitter.
• A scheduled Zap builds a daily report as HTML, publishes it, and posts the fresh link to a channel each morning.
• A new CRM record generates a simple HTML one-pager that sales can share.

Common uses

• Turning form responses, sheet rows, or CRM records into shareable pages.
• Auto-publishing generated reports and emailing or posting the link.
• Sharing files dropped into a cloud folder as clean links.
• Sending a hosted page link instead of an attachment.

Snapy serves static files. Self-contained HTML and documents work well, but anything that needs a live backend or database is out of scope.

Troubleshooting

• No link came back. Confirm payload type is JSON and the content field actually has data mapped into it. An empty content produces no page.
• The link looks like raw code, not a page. Set filename to index.html so Snapy serves it as a web page.
• Binary file is broken. A PDF or image cannot go in content as raw text. Base64 encode it and send content_base64 with a matching filename.
• Name already taken. Pick a different name, or leave name blank to get a random address.

Using the link downstream

The Webhooks step returns JSON, so Zapier surfaces url, stats_url, and token as fields you can map into any later action. Insert url into a Slack message, a Gmail body, a new sheet row, or a database record. Map stats_url if you want the private analytics page logged, and store token if a later Zap needs to manage the link. Passing the same name on each run keeps the address stable, which helps when a downstream tool expects a fixed URL.

Common patterns

• Trigger driven: a new file, form entry, or record fires the Zap, which publishes and shares the link.
• Scheduled: a Schedule by Zapier trigger builds and publishes content on an interval, then posts the fresh link.
• Mid-Zap: an existing Zap adds one Webhooks step to turn generated HTML into a link before the next action.

Each pattern reuses the same single Webhooks step, so adding Snapy to a working Zap is a small change rather than a rebuild.

Good to know

• Free, no account, no API key.
• Works the same way in Make and n8n. See Snapy and Make and Snapy and n8n, or browse all integrations.

Full details are in the developer docs. One Webhooks step turns any Zap output into a link.