Supercharged Webhooks & Slack Alerts

Launch edition: this release note describes a feature in UpdateTinus's early-access preview; details may change before general availability.

Slack, GitHub and Discord are trademarks of their respective owners. UpdateTinus is not affiliated with or endorsed by them, and delivery to these services depends on their availability and terms.

A release note is only useful if it reaches people. Some of your audience reads the public changelog, some see the in-app beacon, and a lot of your own team lives in chat. In v2.4 of the UpdateTinus preview we are introducing supercharged webhooks and Slack alerts, so every announcement can travel to the places where conversations already happen.

Webhooks, rebuilt

Webhooks are the simplest way for one system to tell another that something happened. UpdateTinus now sends an HTTP POST request to any endpoint you configure whenever certain events occur. You choose which events matter:

• note.published when a release note goes live.
• note.updated when a published note is edited.
• roadmap.item_moved when a roadmap item changes status.
• feedback.created when someone posts on a feedback board.
• reaction.summary a periodic summary of emoji reactions on recent notes.

An example payload

Here is a small example of what a note.published event looks like. Field names may still change during early access.

{"event": "note.published", "workspace": "web-app", "note": {"title": "Dark mode for dashboards", "version": "v2.4", "tag": "New Feature", "excerpt": "Dashboards now follow your system theme.", "url": "https://example.com/changelog/dark-mode"}, "sent_at": "2026-09-08T14:00:00Z"}

Every request includes a signature header generated with a secret unique to that webhook. Your receiving service can verify the signature to confirm the request really came from your UpdateTinus workspace and was not altered on the way.

Slack alerts

For Slack, you do not need to write any code. Add a Slack incoming webhook URL to your workspace settings, pick a channel name for reference, and choose which events should post there. Messages are formatted with a clear title, the excerpt, the tag shown as a small label, and a button-style link to the full note.

A few thoughtful defaults keep alerts friendly:

1. Quiet edits. Small edits to a published note do not post a new message unless you ask them to.
2. Digest mode. Feedback and reaction events can be bundled into a daily summary rather than posted one by one.
3. Per-channel filters. Send "Launched" notes to a company-wide channel and everything else to a product channel.

GitHub Discussions and Discord

Open-source projects and developer tools often have communities in GitHub Discussions or on Discord. The new delivery templates format a published note for those destinations too. For GitHub Discussions, a connected workflow can open a new discussion in an announcements category with the full note body. For Discord, a channel webhook receives an embed with title, summary and link. Both rely on credentials you create in those services and can be revoked there at any time.

One announcement, written once, reaching every place your people gather. That is the whole idea.

Reliability and visibility

Webhooks fail sometimes. Endpoints go down, tokens expire, someone renames a channel. Instead of failing silently, UpdateTinus now keeps a delivery log for each webhook showing the event, the response status and the time taken. Failed deliveries are retried with increasing delays for a limited window. If they still fail, the webhook is marked as needing attention and workspace admins are notified inside the app.

You can also send a test event from the settings page at any time. It uses sample content so you can check formatting without publishing anything real.

Security notes

• Webhook secrets are shown once when created; store them in your own secret manager.
• Only HTTPS endpoints are accepted.
• Payloads include public note content only. Drafts, private comments and private roadmap items are never sent unless you build a private webhook and explicitly opt in.
• You can rotate a secret without deleting the webhook, giving your receiver time to switch over.

Ideas for using webhooks

We are excited to see what makers build. A few ideas to spark yours: update a status page when a fix ships, trigger a docs rebuild when a note mentions a new API, post a celebratory message with a custom emoji in your team channel, or feed reaction summaries into a dashboard you already use. Because webhooks are plain HTTP, they work with almost any stack.

What comes next

During early access we are watching which events teams actually subscribe to and where formatting falls short. We are considering richer filtering, templated message bodies, and support for more destinations. None of these are promises yet; they depend on what we learn. If there is a destination or event you are missing, please share it on the feedback board with a short description of your use case.

Getting started

Open your workspace settings, choose Webhooks & Alerts, and add your first endpoint or Slack webhook. Send a test event, check the delivery log, and then publish a real note when you are ready. It is a small setup step that helps every future release reach more of the people who care about it.