Notifications
Send check outcomes to email or HTTPS webhook channels and monitor delivery status.
Loading documentation…
Powered by heyo
Notification channels deliver check outcomes to email recipients or HTTPS webhook endpoints. A schedule controls when notifications are created and which active channels receive them.
Open Channels in the active project and create an Email or Webhook channel. Give it a purpose-specific name and description.
Add up to five email addresses or webhook endpoint URLs. Customer webhook endpoints must use HTTPS; private/internal destinations and IP-literal URLs are not accepted.
A webhook channel can send up to five custom headers. Use a dedicated bearer token or similarly limited credential. Some security-sensitive header names are not accepted.
Start a test from the channel page. It uses the same delivery path as check notifications and creates a message you can inspect.
On each schedule, select the channel and one of the delivery modes below. Only active channels deliver messages.
| Mode | Behavior |
|---|---|
| Never | Do not create outcome notifications for this schedule |
| Always | Notify for successful and unsuccessful terminal outcomes |
| On error only | Notify for failures and timeouts |
Channel delivery is separate from check execution. A successful check can still have a failed notification, and a delivered notification does not change the check result.
Open a channel or a check's Messages tab to inspect delivery. Messages move through queued and delivering states, then end as successful, failed, or permanently failed. A temporary failure may be retried; a permanently failed message will not become successful without a new delivery.
RestoreTrust stores webhook URLs and header values so it can deliver notifications. Never reuse a broad production credential. Create a token with only the receiving endpoint's required permission, rotate it independently, and avoid putting secrets in the URL.
Pause a channel to stop delivery while preserving its configuration. When editing recipients or headers, be prepared to re-enter the complete sensitive set rather than relying on masked values.
A channel cannot be deleted while schedules still reference it. Update those schedules first, then delete the channel if its messages no longer need to be accessed according to your retention needs.