Notifications
Deliver alert and incident updates through configured channels. Secrets are encrypted; webhook hosts are allowlisted.
Channels#
- In-app — workspace inbox.
- Email — Resend when email notifications are entitled (all plans, including Free) and mail is configured.
- Slack, Discord, Microsoft Teams, and generic webhook — via Settings → Integrations.
Outbound webhook payload shape: Webhooks.
Set up, step by step#
Channel integrations (Slack, Discord, Teams, webhook) require Pro (integrations). Email outage alerts for monitors are available on Free when mail is configured.
Step 1: Open Integrations
Go to Settings → Integrations. Until you add a channel the list stays empty.
Step 2: Add a channel
Click New channel or Add channel. Choose Slack, Discord, Microsoft Teams, or Webhook. Paste the incoming webhook URL from that provider, pick auth (None, Bearer, Basic, or HMAC), and select event groups such as Alerts & monitors and Incidents.
Step 3: Test delivery
Use Test on the channel row. A successful test shows “Test message delivered.” Failed tests appear under Delivery history with the last error.
Step 4: Confirm on a real alert
Open or wait for a monitor failure (with email alerts enabled on the monitor create form). Channel fan-out runs from the notification engine — touched / deduped alert updates do not create duplicate open notifications.
When they fire#
Fan-out is driven by the notification engine from alert and incident events (open, escalate, resolve when configured). Touched / deduped alert updates do not create duplicate open notifications.
Configuration#
Manage channels under Settings → Integrations. Channel integrations require Pro (integrations).
Limitations
- No native PagerDuty / Opsgenie connector in the kind enum yet.
- Delivery depends on Trigger workers for retries in production.