Integrations overview
How StatusOwl integrations work: events, testing, and routing to the right channels.
StatusOwl integrations deliver monitor state changes to the tools your team already uses. Every integration is a separate, independently-configured channel — you can create as many as you need, route them at different audiences, and toggle each one on or off without touching the others.
Available integrations
- Email — plain-text alerts to one or more addresses. No OAuth or API key required.
- Discord — rich embeds posted to any Discord channel via an incoming webhook.
- Slack — formatted messages posted to any Slack channel via an incoming webhook.
- Microsoft Teams — adaptive message cards delivered via an Incoming Webhook connector.
- ntfy — push notifications to ntfy.sh or a self-hosted ntfy server, with priority, tags, and optional auth token.
- Webhook — signed JSON payloads POSTed (or PUT) to any HTTPS endpoint you control.
Coming soon
SMS, phone-call escalation, and a native PagerDuty connector are on the roadmap. Until those ship, pipe StatusOwl through a webhook into your existing on-call tool.
Notification events
Each integration independently controls which of three events it fires on. Enable any combination per integration — a single Slack channel can subscribe to everything, while an on-call email gets down events only.
- Monitor down — fired once a monitor crosses its failure threshold.
- Monitor recovery — fired when a previously-down monitor passes again, including the total downtime duration.
- Maintenance mode — fired when a monitor enters a scheduled maintenance window so the team knows the downtime is intentional.
Multiple integrations per type
There is no hard cap on integrations per type. Create one Discord webhook for the on-call channel and another for general engineering; create separate email integrations for internal alerts and customer-facing stakeholders. Each one has its own notification preferences and active/inactive toggle.
Testing before an outage
Every integration has a Send Test button in the dashboard that fires a real test notification immediately. Use this to confirm routing, formatting, and delivery before relying on it in production — no need to intentionally break a monitor.
Permissions
Creating, editing, or deleting an integration requires the Admin or Owner role in the organization. Members can view existing integrations but cannot modify them.