Skip to content

Other channels

These channels are set up the same way as Discord and webhooks — Alerting → Channels → Add a channel — but each needs its own set of fields. Telegram is available on Free; Slack and Google Chat need Pro; ntfy, Microsoft Teams, Splunk, and PagerDuty need Max.

  1. In Slack, create an Incoming Webhook for the channel you want (Slack app settings → Incoming Webhooks).
  2. Copy the webhook URL.
  3. In OKStatus, add a Slack channel and paste the URL.
  1. In Teams, open the channel’s ⋯ menu → Workflows → Send webhook alerts to a channel, and copy the URL it gives. Office 365 connector URLs (webhook.office.com) are refused: Microsoft retired those connectors in 2026 and they no longer deliver.
  2. In OKStatus, add an MS Teams channel and paste the URL.
  1. In the Google Chat space, add a webhook from the space’s app settings and copy its URL.
  2. In OKStatus, add a Google Chat channel and paste the URL.
  1. Create a bot via @BotFather and copy its bot token.
  2. Add the bot to the chat or channel you want notifications in, and get that chat’s chat ID.
  3. In OKStatus, add a Telegram channel with the bot token and chat ID.
  1. Pick a topic name (and, if you’re self-hosting ntfy, your server’s URL and an access token).
  2. In OKStatus, add an ntfy channel with the topic — and the server/token fields if you’re not using ntfy.sh’s default public server.
  1. In Splunk, create an HEC token for the index you want events written to.
  2. In OKStatus, add a Splunk channel with your HEC URL, the token, and optionally the target index. The base URL (https://splunk.example.com:8088) is enough: OKStatus sends to /services/collector/event. A URL with a path is used as given.
  1. In PagerDuty, create a service with an Events API v2 integration and copy its routing key.
  2. In OKStatus, add a PagerDuty channel with that routing key.

Every channel supports Test once created, and the same per-monitor alert kind toggles (up/down, SSL expiry, domain expiry) as Discord, email, and webhooks.