Every release,
straight to #releases.
Drumroll posts a Block Kit card to your Slack channel the moment you publish a changelog entry. No Slack app to install, no OAuth dance - paste an Incoming Webhook URL and you're done. Thirty seconds end-to-end.
How it works
Three steps,
under five minutes.
- 01
Create an Incoming Webhook in Slack
In your Slack workspace: Apps → Incoming Webhooks → Add to Slack → pick a channel → copy the URL. Slack gives you a URL like https://hooks.slack.com/services/T.../B.../...
- 02
Paste into Drumroll
Open Settings → Integrations on Drumroll, find the Slack card, paste the URL, optionally label the channel, hit Connect.
- 03
Test, then publish
The card has a Send test message button - confirm the wiring before you commit. After that, every entry that flips draft → published posts to the channel.
What syncs
Capabilities & limits.
We’re explicit about what Slack sync handles and what it doesn’t. Most teams find the first list covers their actual use; the second is the part vendors usually hide.
Supported
- Slack Block Kit card with title, date, tags, 280-char body preview, and a Read on Drumroll button
- 30-second setup - paste a URL, no Slack App to install or review
- Posts on the first draft → published transition; edits to a published entry don't re-fire
- 10-second timeout, retry-once on transient 5xx; publish flow never blocks on Slack
- Every attempt logged for ops visibility
- Send a test message before trusting it for real events
Not yet supported
- Slack App Directory listing (use Incoming Webhook for v1 - native bot coming later)
- Multiple channels per workspace - one webhook per workspace today
- Posting on entry edits or status flips back to published
- GitHub-sync'd entries don't fire Slack in v1 (manual publish only)
Try it on a real project.
Two minutes to sign up, one click to connect, your team’s shipping rhythm becomes a public page. Always free.
Create a workspace