We publish to a long list of destinations: Telegram channels, Bluesky, Mastodon, Ghost, WordPress, several hosted networks, and more. There was one obvious destination missing from that list: our own site. This post you're reading was published through the fix.
The gap
Every solo founder has a website. Some run it on WordPress or Ghost, which we already support directly. Most don't. They're on Astro, Next.js, Hugo, Webflow, a headless CMS, or something custom they built themselves, and none of those have a standard publishing API we can plug into the way we can with a handful of established platforms. We looked at how other scheduling tools handle this, and almost none of them treat a webhook as an actual publish destination. It's usually just a notification hook that tells some other system a post happened, not a way to deliver the content itself.
So we built one. A Custom webhook channel is a destination you control: any HTTPS endpoint you run, anywhere. Connect it once, and it behaves like any other channel in Bangers. Drafts go to review, you approve, and on schedule, we deliver.
How it works
When a post is ready to publish to a Custom webhook channel, Bangers sends a signed JSON request to the endpoint you gave us, describing the post: a title and body for an article, or plain text for a shorter piece, plus any media. Your endpoint receives it, does whatever you want with it, ghosts it into a database, renders it as a page, whatever your site needs, and replies with a success status.
The signing is what makes this safe to expose publicly. Every request carries an HMAC-SHA256 signature computed over the timestamp and the raw request body, using a secret only you and Bangers know. Your endpoint recomputes that signature and compares it before trusting anything in the payload, which means a request that didn't actually come from Bangers gets rejected before it touches your site.
This blog is the real example. We didn't have a bespoke publishing pipeline for it, so we built the Custom webhook channel, pointed a connection at our own blog's receiving endpoint, and now articles approved inside Bangers show up here the same way any customer's webhook-connected site would receive them.
Who this is for
If your site runs on Astro, Next.js, Hugo, Webflow, or a CMS that isn't WordPress or Ghost, this is your path to publishing through Bangers without us needing a bespoke adapter for your particular stack. You write the small amount of code that receives the request and does something with it, and everything upstream of that, drafting, review, scheduling, approval, works exactly like every other channel.
It's also a natural fit if you already route work through an automation tool like n8n, Zapier, or Make. Point the Custom webhook channel at a catch-hook trigger in whichever of those you use, and you can fan the signed payload out anywhere from there: a database, a second CMS, an internal Slack alert, a static site rebuild. The payload is plain JSON, so it drops into an existing automation without much translation work.
What it isn't
A Custom webhook channel isn't a way to bypass approval. The same review step applies before anything gets sent, same as every other channel we support. It's also not a general integration platform: it delivers what you approve, on schedule, to one endpoint you specify. If your endpoint is down or returns an error, that's a failed publish like any other, and you'll hear about it the same way you'd hear about a failure anywhere else: quickly, with a reason, and a way to retry.
Where to start
If you want to wire this into your own site or automation, the full reference, including request format and signature verification code, is at /docs/webhook.
Next step
If you've been wondering how to get Bangers publishing to your own site, this is how, and this post is the proof it holds up. Get early access if you're not in yet.