Notification Channels

Notification channels receive monitor status changes. A new workspace needs a channel configured and attached to its monitors before you can rely on alerts.

Choose a destination

The dashboard offers the channels available to your workspace. Depending on configuration and plan, these include email, Slack, Discord, Microsoft Teams, Google Chat, Telegram, webhooks, Ntfy, PagerDuty, OpsGenie, and Grafana OnCall. Use the provider-specific fields in the editor; do not reuse an upstream bot account or assume a provider is configured for Probed.

Webhook-based integrations need a destination URL with permission to post. Provider tokens and webhook URLs are secrets. Confirm delivery after creating or changing a channel, and verify recovery notifications as well as failures.

Custom webhooks

Custom webhooks send an HTTP POST with JSON describing the monitor and status. The status is error, degraded, or recovered; fields such as latency, status code, and error message depend on the check result.

These requests do not carry a payload signature or HMAC. Configure a secret header and validate it at your receiver. Use HTTPS and reject requests that fail your verification.

Monitor notifications and status-page subscriber messages serve different audiences. Review the notification choice when publishing reports.