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.

Slack

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.

Microsoft Teams

1. In Teams, add a Workflow (or the legacy Incoming Webhook connector, depending on your tenant) to the channel and copy its URL.
2. In OKStatus, add an MS Teams channel and paste the URL.

Google Chat

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.

Telegram

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.

ntfy

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.

Splunk (HTTP Event Collector)

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.

PagerDuty

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.