Skip to the page

n8n and Make

n8n and Make call the Buzzmark API from n8n's HTTP Request node or Make's HTTP module, with your key in the Authorization header.

A run that creates something sends an Idempotency-Key that stays the same when the run retries, so it never posts twice. A Buzzmark webhook can start a workflow when a post goes out or fails.

n8n

  1. 1. Add an HTTP Request node. Press Import cURL and paste the curl example from the endpoint on Endpoints: n8n fills in the method, the address, the headers and the body.

  2. 2. Under Authentication, pick Generic Credential Type, then Header Auth, and make a credential with the name Authorization and the value Bearer followed by your key. Remove the Authorization header the import added, so the key lives only in the credential.

  3. 3. For a request that creates something, set the Idempotency-Key header to a value that's the same each time this item is sent, such as the id of the row or post the workflow started from.

  4. 4. Run the node once to see the answer, then map its fields into the next node.

Turn on Retry On Fail in the node's settings for answers worth a retry: the error's retryable says which. A retry with the same Idempotency-Key gets the first answer, never a second post.

Make

  1. 1. Add the HTTP app's Make a request module, and set the address from the endpoint on Endpoints, such as https://buzzmark.ai/api/v1/posts, and its method.

  2. 2. Under Headers, add Authorization with the value Bearer followed by your key, and Idempotency-Key for a request that creates something.

  3. 3. For a body, pick Raw as the body type and JSON (application/json) as the content type, and put the example's JSON in Request content, with your scenario's values mapped in.

  4. 4. Turn on Parse response, so the next module can map the answer's fields.

Use a value from the item the scenario started from as the Idempotency-Key, such as a row id, so running the scenario again on the same item never posts twice.

Start a workflow from a webhook

To run a workflow when a post goes out or fails, add n8n's Webhook trigger or Make's Custom webhook, and paste its address into Endpoint under Webhooks in Buzzmark. Press Send test event so the workflow sees an event's shape.

Each event is JSON with its type and data: a post's id, status and time, never its words. Branch on type, read the rest with GET /posts/{id}, and keep Buzzmark-Event-Id so an event sent twice runs once. Webhooks has every event and how to check the signature.

Workflows you can build

  • A new post on your blog becomes a draft in your brand's voice, with POST /write and POST /drafts.
  • A row in a sheet schedules a post with POST /posts and when: next_slot.
  • post.failed and account.needs_reconnect post a message to Slack.
  • A contributor's key drafts from a form, and an owner approves in Buzzmark.

Where to next