StatusPage.me Help Center

Popular topics: creating a status page, connecting monitors, automatic incidents, custom domains, integrations and billing.

StatusPage.me Dec 9, 2025 Notifications

Notification Channels Overview

Notification channels are how you receive alerts for incidents and monitor events. Configure channels once, then link them to one or more status pages.

Notification channels settings

What Are Notification Channels?

A notification channel is a destination for your alerts. You can create multiple channels (for different teams/tools) and enable/disable them per status page.

These channels are for owner/team alerts. Public status page subscribers are configured separately and can optionally use per-component subscriber delivery filters.

They are also separate from your personal dashboard alert preferences, such as browser notifications, the notification bell, and incident alarm sounds. For those account-level settings, see Personal Notification Preferences.

Where you manage them

  • Create/edit channels: /user/status-pages/notifications
  • Link channels to a status page: /user/status-pages/{status_page_id}/settings#notifications
  • Audit everything in one place (matrix): /user/notifications/hub

If you want incidents to automatically route to a rotating on-call person (with escalation), see: On-Call Scheduling.

Team Channels vs. Personal Alerts

It is common to use both systems together:

  • Notification channels send alerts to your shared destinations such as Slack, email, PagerDuty, webhooks, or SMS
  • Personal alerts control how your own signed-in dashboard session behaves

Personal alerts include:

  • browser notifications for incidents
  • the in-app notification bell and full notification history
  • optional critical incident alarm sounds

Configure those personal preferences here: Personal Notification Preferences.

Available Channel Types

IconChannelDescriptionSetup guide
DiscordRich embed notifications land directly in your Discord channels — perfect for dev teams and communities. Paste a webhook URL and you're done.Jump to setup
SlackFormatted block messages with thread support keep your workspace informed. Configure a bot token + channel ID and route alerts to the right channel.Jump to setup
TelegramInstant push notifications via a Telegram bot — great for on-call engineers and small teams who live on mobile. Supports groups and channels.Jump to setup
WebhooksPOST structured JSON to any endpoint — pipe events into Zapier, Make, n8n, or your own microservices. Custom headers, a body template, and auth are all supported.Jump to setup
EmailHTML-formatted incident emails with direct links — the reliable fallback that works on every device. Your account email is enabled by default.Jump to setup
Microsoft TeamsAdaptive cards with status colors and action buttons surface directly in Teams conversations. Enterprise-grade security, zero extra config.Jump to setup
PushoverNative push notifications on iOS and Android with priority levels and custom sounds. Critical alerts break through Do Not Disturb.Jump to setup
PagerDutyTrigger and auto-resolve PagerDuty incidents via Events API v2 so your on-call flow stays aligned with monitor failures and recoveries.Jump to setup
Google ChatSend alerts to Google Chat spaces using an incoming webhook URL. Fast to set up, great for teams already on Google Workspace.Jump to setup
MattermostRoute incident and uptime alerts into Mattermost via incoming webhook. Ideal for self-hosted chat setups and ops teams.Jump to setup
Rocket.ChatDeliver alerts into Rocket.Chat using an incoming webhook URL. Works well for self-managed environments and internal teams.Jump to setup
SMSText message alerts via your own Twilio, Vonage, MessageBird, or Esendex account — a delivery path that works with no app and no internet connection.Jump to setup
ntfyPush alerts to the public ntfy.sh server or your own self-hosted instance. No account required — pick a topic and go.Jump to setup
GotifyDeliver alerts to your self-hosted Gotify server. A lightweight, self-managed alternative to commercial push services.Jump to setup
MatrixPost alerts directly into a Matrix room on your own homeserver — an open, federated alternative to hosted chat platforms.Jump to setup
WhatsAppSend incident alerts to WhatsApp via your own Twilio account — reach teams and on-call engineers wherever they already are.Jump to setup
Voice CallAn automated phone call reads the alert aloud — the escalation path for when a push notification isn't enough to wake someone up.Jump to setup
Jira Service ManagementRaise and auto-resolve alerts in Jira Service Management Operations — the supported successor to Opsgenie.Jump to setup
ServiceNowOpen incident records in ServiceNow directly from monitor and status page events.Jump to setup

Setting Up Email Notifications

Email channels support one or more recipients.

  1. Go to /user/status-pages/notifications
  2. Click Add Channel → Email
  3. Add recipient email addresses
  4. Save the channel
  5. Confirm the verification email (so it shows as Verified)

Setting Up Webhooks

Webhooks send an HTTP request to your endpoint.

  1. Go to /user/status-pages/notifications
  2. Click Add Channel → Webhook
  3. Enter the destination URL
  4. Choose the HTTP method (POST/PUT)
  5. (Optional) Add custom HTTP headers as JSON
  6. Save the channel

Payload format:

  • Webhook sends JSON { "subject": "…", "message": "…" } by default.
  • Google Chat / Mattermost / Rocket.Chat send JSON { "text": "…" }.

Custom body template. For full control over the request body, add an optional
Body Template and Content Type when creating a webhook channel. The template
receives:

  • .Subject, .Message — the alert’s title and body
  • .Severity — critical, warning, resolved, or info
  • .Timestamp — RFC 3339, UTC
  • .Fields — a map of the alert’s parsed key/value fields (e.g. {{ index .Fields "Monitor" }})
  • .FieldList — the same fields, in order, as {Name, Value} pairs — use this if you need to range over them

Example, for a service that expects {"text": "..."}:

{"text": "{{ .Subject }} ({{ .Severity }})\n{{ .Message }}"}

This is what lets the webhook channel talk directly to Zapier, Make, n8n, Home Assistant,
Alertmanager-compatible receivers, or any in-house consumer without a dedicated
integration for each. Leave the template empty to keep the default payload.

Setting Up Slack

Slack channels use a Slack App bot token and a Channel ID.

  1. Go to /user/status-pages/notifications
  2. Click Add Channel → Slack
  3. Paste your Bot Token (starts with xoxb-)
  4. Paste the target Channel ID (e.g. C0XXXXXXXXX)
  5. Ensure your bot is allowed to post in that channel (invite it if needed)
  6. Save the channel

Setting Up Discord

  1. Create a webhook in your Discord server settings
  2. Copy the Webhook URL
  3. In /user/status-pages/notifications, add a Discord channel and paste the URL
  4. Save, then send a test

Setting Up Telegram

Telegram supports two modes:

  • Use Our Bot (Easy): you only provide your Chat ID
  • Use Custom Bot: you provide a Bot Token + Chat ID
  1. Go to /user/status-pages/notifications
  2. Click Add Channel → Telegram
  3. Choose Use Our Bot or Use Custom Bot
  4. Get your Chat ID and paste it in
  1. If using Custom Bot, paste your Bot Token from @BotFather
  2. Save the channel and send a test

Setting Up Microsoft Teams

  1. Open the target Teams channel and create an incoming webhook
  2. Copy the webhook URL
  3. Add it as an MS Teams channel in /user/status-pages/notifications
  4. Verify delivery with a test notification

Setting Up Pushover

  1. Create a Pushover application and note the app token
  2. Copy your Pushover user key
  3. Add a Pushover channel in /user/status-pages/notifications with the token + user key
  4. Send a test notification to validate the connection

Setting Up SMS

SMS notifications use your own provider account. Supported providers: Twilio, Vonage (Nexmo), MessageBird, Esendex.

  1. Go to /user/status-pages/notifications
  2. Click Add Channel → SMS
  3. Select your provider and enter the required credentials
  4. Enter a Sender / From Number and one or more Recipient Numbers (E.164 format)
  5. Configure cost controls (dedup window, daily limit) and select which events trigger an SMS
  6. Save and send a test

SMS messages are truncated to 160 characters. Per-provider message IDs are recorded in Notification History so you can look them up in your provider’s console.

For full setup instructions and troubleshooting, see SMS Notifications.

Setting Up PagerDuty

PagerDuty integration uses the Events API v2 to trigger and auto-resolve incidents.

  1. In PagerDuty, create or open a Service
  2. Add an Events API v2 integration to that service
  3. Copy the Integration Key (also called Routing Key)
  4. In /user/status-pages/notifications, add a PagerDuty channel and paste the key
  5. Save and send a test notification

How events map to PagerDuty:

  • Monitor Down / Heartbeat Missed / New Incident -> triggers a PagerDuty incident (severity: critical)
  • Response Degraded -> triggers a PagerDuty incident (severity: warning)
  • Monitor Recovered / Incident Resolved / Heartbeat Recovered -> resolves the PagerDuty incident
  • Maintenance -> triggers a PagerDuty incident (severity: info)

For a detailed guide, see PagerDuty Integration.

Setting Up Google Chat

Google Chat uses an incoming webhook URL. This channel type uses the same fields as Webhook (URL, method, optional headers), but sends a { "text": "…" } JSON payload.

  1. Create an incoming webhook in Google Chat
  2. Copy the webhook URL
  3. Add a Google Chat channel in /user/status-pages/notifications
  4. Save and send a test

Setting Up Mattermost

Mattermost uses an incoming webhook URL. This channel type uses the same fields as Webhook (URL, method, optional headers), but sends a { "text": "…" } JSON payload.

  1. Create an incoming webhook in Mattermost
  2. Copy the webhook URL
  3. Add a Mattermost channel in /user/status-pages/notifications
  4. Save and send a test

Setting Up Rocket Chat

Rocket.Chat uses an incoming webhook URL. This channel type uses the same fields as Webhook (URL, method, optional headers), but sends a { "text": "…" } JSON payload.

  1. Create an incoming webhook in Rocket.Chat
  2. Copy the webhook URL
  3. Add a Rocket.Chat channel in /user/status-pages/notifications
  4. Save and send a test

Setting Up ntfy

ntfy is a simple pub-sub push service. Use the public ntfy.sh server or point it at your own self-hosted instance — no account required either way.

  1. Pick a topic name. Anyone who knows the topic can read it, so choose something unguessable (not “alerts”)
  2. (Optional) Set a Server URL if you’re self-hosting; leave blank to use https://ntfy.sh
  3. (Optional) Add an Access Token if your topic requires authentication
  4. Add an ntfy channel in /user/status-pages/notifications with these values
  5. Subscribe to the topic in the ntfy app or web client, then save and send a test

Setting Up Gotify

Gotify is a self-hosted push notification server.

  1. Create an application in your Gotify server and copy its Application Token
  2. Add a Gotify channel in /user/status-pages/notifications with your Server URL and the application token
  3. Save and send a test notification

Setting Up Matrix

Post alerts into a room on your own Matrix homeserver.

  1. Get the Room ID for the target room (starts with !, e.g. !abcdef:matrix.org)
  2. Create an access token for a bot/service account on your homeserver
  3. Add a Matrix channel in /user/status-pages/notifications with the Homeserver URL, Room ID, and Access Token
  4. Save and send a test

Setting Up WhatsApp

WhatsApp alerts use your own Twilio account and WhatsApp sender.

  1. Set up a WhatsApp sender in your Twilio console
  2. Add a WhatsApp channel in /user/status-pages/notifications with your Twilio Account SID, Auth Token, sender number, and recipient numbers (E.164 format)
  3. Save and send a test

Twilio only allows free-form business-initiated messages within 24 hours of the recipient’s last reply. Outside that window, your Twilio account must use a pre-approved message template — configure this on the Twilio side.

Setting Up Voice Call

An automated call that reads the alert headline aloud, twice — the escalation path for when a push notification alone isn’t enough to wake someone up. Reserve this for critical events.

  1. Add a Voice Call channel in /user/status-pages/notifications with your Twilio Account SID, Auth Token, caller number, and recipient numbers (E.164 format)
  2. Save and send a test — you should receive a call reading the alert aloud

Setting Up Jira Service Management

Jira Service Management (JSM) Operations is the supported successor to Opsgenie for triggering and resolving on-call alerts.

  1. In Atlassian, note your Cloud ID, your account email, and generate an API token
  2. Add a Jira Service Management channel in /user/status-pages/notifications with those three values
  3. Save and send a test notification

Alerts use the same alias-based dedup as PagerDuty, so a recovery closes the alert its outage opened instead of stacking a new one.

Setting Up ServiceNow

Open an incident record in your ServiceNow instance directly from monitor and status page events.

  1. Create (or reuse) an integration user in ServiceNow with permission to create incidents
  2. Add a ServiceNow channel in /user/status-pages/notifications with your Instance URL and the integration user’s credentials
  3. Save and send a test — a new incident record should appear in your instance

Testing Notifications

Always test your channels before relying on them:

  1. Go to /user/status-pages/notifications
  2. Click Test next to any channel
  3. Verify you receive the test notification
  4. If not, check your configuration

Linking Channels to Status Pages

After you create channels, you enable them per status page:

  1. Open your status page settings: /user/status-pages/{status_page_id}/settings#notifications
  2. Click Link Channel
  3. Select a channel and link it
  4. Toggle channels on/off for that status page

You can also set component notification overrides to use a different set of channels for a specific component.

Notification Hub - Unified Management

The Notification Hub provides a centralized view of all your notification channels and status pages in one place.

Using the Notification Hub

  1. Go to Notification Hub in the left menu
    • Direct URL: /user/notifications/hub
  2. View the Channel × Status Page matrix
  3. Click a status page name to jump to its notification settings

For more details, see Notification Hub Guide.

Best Practices

DoDon’t
Use multiple channels for critical servicesRely on a single channel
Test regularlyAssume channels are working
Keep at least one email channel enabledMake chat apps your only delivery path

What’s Next?

Connect your notification channels
Start free trial No credit card required
Was this article helpful?
On this page

Loading table of contents...

Related Articles
Managing Status Page Subscribers

Let users subscribe to your status page for automatic updates, with optional per-component delivery filters.

Personal Notification Preferences

Manage the notification bell, browser notifications, and incident alarm behavior for your own account.

Per-Component Subscriber Notifications

Let visitors subscribe only to the services they care about on your status page.

Notification Hub - Unified Channel Management

Manage all your notification channels across multiple status pages from one centralized location.

PagerDuty Integration

Connect PagerDuty to your status page for automatic incident triggering and resolution.