Webhooks for Make, Zapier and your own tools

Send a signed message to another tool when a pin is published, a pin fails or a post is imported.

Webhooks let other tools react to what happens in Bloomtack, for example adding a row to a spreadsheet when a pin is published.

Events

Pin published (pin.published in the message): a pin went live on Pinterest.
Pin failed (pin.failed): a pin could not be published, with its error ID and whether it will be tried again.
Post imported (post.imported): a new post arrived from your blog.

Set one up

Open Settings, then Webhooks. Owners and admins can.
Paste the Endpoint address, an https:// address that accepts POST requests, add a Note (optional) if you like, pick the events, and press Add endpoint.
Copy the signing secret with Copy secret and keep it in the receiving tool. It is not shown again; press I saved it when done.
Press Send test event to try it. Show deliveries lists every delivery with its result, and Retry sends a failed one again.

With Make or Zapier

Use their generic webhook trigger, paste its address into Bloomtack, and build the rest of the flow there. Bloomtack has no separate Make or Zapier app.

Checking messages are really from us

Messages follow the Standard Webhooks format: each carries a message ID, a timestamp and a signature made with your signing secret. Check the signature and the timestamp before trusting a message; Standard Webhooks libraries do it for you. New secret replaces the secret if it leaked.

When your endpoint is down

A failed delivery is tried again on a schedule for about 3 days. After 24 hours without one success, owners and admins are told; after 5 days, the endpoint is turned off. Turn on starts it again; Remove deletes it with its secret and log, after you type its address.

Good to know

Bloomtack has no public API; webhooks cover the common automations.

Updated October 4, 2026.