Webhook
Wire alerts into whatever you already run
A structured JSON POST built for your own tooling to parse, not for a human to read in a chat window.
- One POST per event, JSON body, no signing or auth headers to configure
- Full issue detail (id, title, status, exception class, event count, a link back in) or heartbeat detail, whichever triggered it
- The same delivery path Slack uses under the hood, just a different payload shape
A payload meant for code, not a chat client
Where Slack gets a formatted message, a generic webhook rule gets a plain JSON object: { trigger, issue: { id, title, status, exception_class, events_count, url } } for an issue-based trigger, or the equivalent heartbeat shape for a missed heartbeat. That's deliberately the raw data, not prose, so it's easy to route into your own on-call tool, a custom dashboard, or anything else that can accept a POST.
Point it at an internal endpoint, a generic automation tool, or anywhere else that takes a webhook -- the target field just needs to be a reachable http(s) URL.
Webhook uses the exact same rule form as every other channel.