Skip to content

Email integration

Send plain-text alert emails to one or more addresses.

Last updated May 9, 2026

The Email integration delivers alerts directly to any inbox. It's the simplest channel to configure — no OAuth, no webhook, no API key.

Setting up Email

  1. Go to Integrations → Add Integration and choose Email.
  2. Give the integration a name (e.g. On-call inbox).
  3. Enter one or more email addresses, separated by commas or new lines.
  4. Choose which events you want this integration to receive (see event coverage for what currently fires).
  5. Click Save, then Send Test to confirm delivery.

Multiple addresses per integration

A single email integration can fan out to several recipients. For distinct routing rules — customer-facing vs. engineering, on-call vs. broadcast — create separate integrations so each has its own event selection and on/off toggle.

Prefer a distribution list or alias (e.g. oncall@yourcompany.com) over hardcoding individual addresses. That way you can rotate the on-call roster in your email provider without editing StatusOwl.

What currently sends to this integration

Per the integrations overview, Email integrations receive:

  • Send Test events from the dashboard — useful for confirming routing immediately after setup.
  • Watch Owl alert rules — when a host-metric rule routes to this integration, the firing and resolving emails land here.

Uptime-monitor state changes (down / recovery / maintenance) are configured on the integration but not yet dispatched. The flags are ready for the dispatch service when it ships.

Deliverability

Alerts are sent from a verified StatusOwl sending domain with proper SPF, DKIM, and DMARC records. If messages land in spam for your recipients, add the sender address to your corporate allowlist.

For high-volume inboxes (alerts shared with a large team), consider fronting StatusOwl with a transactional-email provider via the Webhook integration — your provider's infrastructure handles list management, suppression, and bounce handling.

See also