Notification channels

A notification channel is a destination for alerts. Open Settings → Notification Channels, click Add Channel, pick a type and fill in its fields. Team members and administrators can add, edit, test and delete channels; viewers can only look at them.

Supported channels

| Channel | What you enter | Notes | |---------|----------------|-------| | Email | One email address | The address must be verified before it receives alerts. | | Slack | Incoming webhook URL starting with https://hooks.slack.com/ | | | Discord | Channel webhook URL starting with https://discord.com/api/webhooks/ | | | Webhook | Any public URL, method (POST, PUT or PATCH), optional headers and signing secret | JSON body, optional X-Webhook-Signature HMAC header. | | Telegram | Nothing; you link a chat to the bot after saving | Send the /start command shown on the channel's edit page. | | PagerDuty | Events API v2 routing (integration) key | Opens an alert and resolves it on recovery. | | Microsoft Teams | Incoming webhook URL | Alerts are sent as Adaptive Cards. | | Opsgenie | API key and region (US or EU) | Opens an alert and closes it on recovery. | | Google Chat | Space webhook URL | | | Pushover | User key and application API token | | | Ntfy | Topic, and optionally your own server URL | Uses https://ntfy.sh when no server is given. |

Webhook-style destinations must be publicly reachable. Requests to private or internal addresses are refused.

Which events each channel receives

| Event | Channels | |-------|----------| | Site down and site recovered (confirmed incidents, including missed heartbeats) | All channels | | TLS certificate expiring and renewed | All channels | | DNS record changed and restored | All channels | | Scan issue and scan resolved (broken links, mixed content, TLS scan findings, application health) | All channels | | Performance degraded and recovered | Email and Telegram only |

Performance alerts are off by default. Turn them on per HTTP check. Other channel types do not deliver performance events, so they are not offered for them.

Which channels a site uses

If you assign channels to a site, only those channels receive its alerts, filtered by the alert types you tick for each channel on that site (downtime, recovery, TLS expiry, DNS changes, link scans, application health and performance). If a site has no assigned channels, every enabled channel of the team receives its alerts.

Disabled channels and unverified email channels receive nothing. While a site is snoozed or inside a maintenance window, new issue alerts are recorded as suppressed. A recovery still goes to each channel that received the original issue, so PagerDuty and Opsgenie can close the alert they opened.

Testing and delivery

Use Send Test on a channel to check the destination. A test only proves that the destination accepts a message; it does not simulate an outage. Tests are limited to six per minute.

If a destination fails, delivery is retried automatically up to eight times over about four hours (after 1, 2, 5, 10, 30, 60 and 120 minutes). Delivery to one channel does not wait for the others.

See the articles for each channel type for setup details.