Sume with Zapier, Make or n8n: no app in the docs, so use HTTP

We found no Sume app for Zapier, Make or n8n in Sume's docs, so the working pattern is generic: start a run with an HTTP request using your Bearer API key, give the run a communication.webhook_url that points at the tool's incoming-webhook address, and read the receipt by polling if the delivery never arrives. This is an absence claim from the docs we read, not a statement about every marketplace listing, so check the tool's own app directory before you build.

What each side must provide

Sume's side is documented: POST /v1/formats/{handle}/{slug}/runs with formats:write, a receipt that returns right away, and a signed terminal webhook. The automation tool's side comes from its own help pages, which we read today.

Steps

The same four steps work in all three tools.

• Create the incoming-webhook trigger and copy its production address.
• Add an HTTP request step that POSTs to the Sume run route with Authorization: Bearer and an Idempotency-Key made from your own row id.
• Put the trigger address in communication.webhook_url on that request, and store the returned arun_ id.
• Add a second path that reads GET /v1/format-runs/{run_id} on a timer, so a missed delivery is still caught.

What Sume does not do

Sume does not ship a trigger that these tools can subscribe to, and a service-account key cannot create Format runs, so the key in your HTTP step must be a normal key with the right scopes and, for a team Format, issued in that workspace. The tools do not verify Sume's signature unless you add that step yourself; a Zapier Catch Hook, for example, accepts what is posted to it.

Sume's retries cover a refusing endpoint for up to ten attempts, but a tool that returns 200 and then delays processing will look healthy to Sume while your workflow lags, so poll as a backup. If the docs add a native connector later, this post will be out of date.

Choosing between the three

The choice rarely turns on Sume. Zapier is the quickest for a single trigger and a couple of actions, Make is strong when you want to branch and loop visually, and n8n is the one you can self-host. The limits in the table are the ones that bite a holiday batch: payload size for a large receipt, request rate for a burst, and what happens when the automation is switched off. Sume's receipt payload is null above 1 MiB with a result URL to fetch, which is far below the payload limits of the three tools, so size is rarely the problem.