Skip to content
StatusOwlDocs

Email

Deliver alerts to one or more inboxes. The simplest channel to configure.

Last updated

The Email integration delivers to any inbox. No OAuth, no webhook, no API key — it is the fastest channel to get working, and the one worth setting up first just to confirm the path end to end.

Setting it up

  1. Go to Integrations → Add Integration and choose Email.
  2. Name it something you will recognise later — On-call inbox, not Integration 3.
  3. Enter one or more addresses, separated by commas or new lines.
  4. Click Save, then Send Test and confirm it arrives.

Multiple addresses

One email integration can fan out to several recipients. Create separate integrations when the recipients need different routing — engineering versus stakeholders, on-call versus broadcast — because routing is chosen per Watch Owl alert rule, per integration.

Point at an alias, not at people

Use a distribution list — oncall@yourcompany.com — rather than listing individuals. You can then change who is on call in your email provider without touching StatusOwl, and nobody's alerts vanish when they leave.

What arrives here today

  • Send Test messages from the dashboard.
  • Watch Owl alert rules routed to this integration — one message when a rule fires and one when it resolves, carrying the rule name, the host, the metric and its value, the threshold and the timestamp.

That is the full list. A failing HTTP, ping or TCP check does not email you — see Notifications overview.

Separately from integrations, StatusOwl can email you a periodic uptime report — daily, weekly or monthly. That is configured under report preferences, not here.

Deliverability

Alerts are sent through Resend from a verified StatusOwl sending domain with SPF, DKIM and DMARC in place. If messages land in spam for your recipients, add the sender to your allowlist — a corporate filter that quarantines alert mail is worse than no alert mail, because you will believe it is working.

See also