Outbound: where alerts go
- Slack — post incident summaries directly into channels.
- Microsoft Teams — notify Teams channels without extra connectors.
- Discord — fast alerts into community or ops servers.
- PagerDuty — trigger incidents and let escalation policies run.
- Email — simple, reliable inbox notifications.
- SMS — high-signal alerts for urgent incidents (PAYG on paid plans).
- Outbound Webhooks — forward JSON payloads into any custom system.
Control routing and quiet hours with Notification Policies.
Inbound: webhook receipt monitoring
If a provider should be calling you — payments, CRMs, CI/CD pipelines, or scheduled jobs — you can issue a unique Webhook Receipt monitor. We expect heartbeats/events at the cadence you define, and we alert if they stop or arrive late.
- Unique URL per integration (just paste into the provider)
- Cadence windows (every N minutes/hours/days)
- Shared secret headers for validation
- Alerts on missed or late events
Setup in three steps
Outbound or inbound — integrations stay simple.
1) Pick destination or monitor
Choose Slack/Teams/Discord, PagerDuty, Email, SMS — or create a webhook receipt monitor.
2) Configure policies
Map alerts and receipts to the right people using Notification Policies.
3) Test and go live
Send a test alert or wait for first receipt. Confirm payloads, cadence, and channels.
Stay connected, inside and out
Push alerts where your team works. Verify inbound events keep flowing. One platform, both directions covered.
Connect integrations