Add a destination once, then reference it from any notify step in any policy. Nothing needs to be configured twice, and a single outage can reach a channel, a phone and an incident tool in whatever order you drew.
Chat destinations use an incoming webhook, so setup is a matter of pasting a URL. No app to install and no permissions to review.
Post to any channel through an incoming webhook. The most common first destination, and usually the one that stays.
Post to a channel through a webhook. Popular with smaller teams and communities running their own infrastructure.
Post to a channel through an incoming webhook, for teams already living in the Microsoft stack.
Send routine alerts to a general channel and critical ones to a dedicated incident channel, decided on the canvas.
Channels are good at informing a team and bad at waking one person. These destinations reach an individual.
Built in with nothing to set up. Send to your own address or any team member, with an optional acknowledge link so the recipient can claim the incident.
Text a number through your own Twilio account. The most reliable way to reach someone who is not looking at a screen.
An email step can page whoever is on duty right now instead of a fixed recipient, so the rota does the routing.
Chain email steps with waits in between and an unclaimed page moves to the next engineer automatically.
Trigger an incident on the Events API. It resolves itself when the monitor recovers, so nothing is left open by hand.
Open an issue in a project when a monitor goes down and close it on recovery using the same key. Useful when outages need a paper trail.
POST to any URL with an optional bearer token. The escape hatch for anything not on this list, including your own internal tooling.
Not a notification but an action: call an endpoint to restart a service, scale a group or kick off a runbook before a human is involved.
Each step fires once per incident by default, or on every matching check when you want a steady drumbeat until something changes.
A cooldown per step, so a service bouncing up and down does not turn into a hundred messages.
Put a noisy destination behind set hours and days while leaving the critical path open around the clock.
Because policies belong to monitors, the same Slack connection can be used loudly by one service and sparingly by another.
Paste a webhook URL, draw a line to it, and watch a real check fire through to your channel.