A message in your channel the moment something breaks
Slack
Your customers find out from your status page. Your team should find out sooner, in the place they are already looking.
Dashboard → Notifications → Slack. This requires the Slack alerts capability, which sits on top of Monitoring.
Setting it up
- Create an incoming webhook in your Slack workspace for the channel you want.
- Paste the webhook URL into the Slack panel and save.
- Send a test message to confirm it lands in the right channel.
What arrives
A message when a monitor goes down, and a message when it recovers, naming the service and the time. A warning also arrives when a certificate is close to expiry. Domain-registration warnings require a separately enabled rollout and are paused by default.
These follow the monitor state directly, so they arrive after two consecutive failed checks, not after the fifteen-minute grace that governs publishing to your customers. That gap is the point: your team hears about it during the window in which fixing it quietly is still an option.
Choosing the channel
Send it where somebody is actually on call. A channel that pages the right people beats a general engineering channel where a red message at 03:00 scrolls past unread.
Incidents in chat
Slack carries monitor alerts. If what you want in a channel is the incidents and maintenance you publish, the same stream your subscribers get, use a Discord, Microsoft Teams or Telegram destination. The WhatsApp development preview describes both kinds of alert on a named person's phone; production delivery remains disabled.
Somewhere other than chat
For your own systems, an on-call tool, a bot, an internal dashboard, use webhooks: signed HTTP POSTs for the events you pick, with delivery logs and redelivery. The Billing screen shows the webhook capacity enabled for this account.