Turn every new article into a webhook

A JSON body with the event type (article.published), a test flag, a timestamp, your campaign name, the article URL, and a ready-to-post message generated from the article. Every request also carries an X-Broadcast-Event header identifying the event type.

Set a secret when you connect the webhook. Every request then includes an X-Broadcast-Signature header containing sha256= followed by the HMAC-SHA256 of the raw request body, computed with your secret. Recompute it on your side and reject anything that doesn't match.

Yes. All three offer a webhook trigger that gives you a URL to paste into Broadcast: the Webhook node in n8n, the custom webhook trigger in Make, and Webhooks by Zapier. The test payload sent on connect lets you map the JSON fields right away.

Yes, automatically. When you connect or update the endpoint, Broadcast immediately sends a test payload with "test": true and only saves the integration if your endpoint answers successfully.

When your newsletter goes out. Broadcast follows your campaign schedule (as soon as a new article is detected, daily, weekly, or monthly). In manual mode, you review the generated message first and the webhook fires when you approve it.

No. The Discord integration posts a formatted message straight into a channel via a Discord webhook, no configuration needed. The generic webhook calls your own endpoint with a JSON payload, for anything you want to build on top.

Webhooks are part of the paid plans, and every paid plan starts with a free trial. The free plan covers the newsletter itself. See the pricing page for details.