Email-to-alert integration

Turn alert emails into calls, Telegram and escalation

Every legacy tool can send an email. Give each WardenPoint integration its own inbound address, point your monitor's alert email at it, and we parse the subject and body into a routed, acknowledgement-aware alert.

Start free View API examples
Setup
One address
Parsing
Subject + body
Channels
8

Anatomy of an alert email

LIVE
Your tool → email
[CRITICAL] Disk 91% on db-primary
WardenPoint
critical · escalate · ack · resolved notice
Telegram
Voice call
Email

Setup

Three steps, no webhook code

Anything that can send an email can drive WardenPoint — cron jobs, appliances, SaaS tools without a webhook, or a legacy monitor you can't change.

  1. 1Step 1

    Create an Email integration

    In Alert integrations, add a source of type Email. We mint a unique inbound address for it — your capability key, not a shared mailbox.

  2. 2Step 2

    Point your monitor at the address

    Paste the address wherever your tool sends alert notifications. No API key, no signature — the address itself is the secret.

  3. 3Step 3

    Pick how emails become incidents

    Choose Smart correlation so a firing email and its later recovery collapse into one incident, or one alert per email. Add a sender allowlist if you want to lock it to known domains.

Wire format

What we read from an email

The subject becomes the title; severity and firing/resolved come from keywords. Need exact control? Add structured lines to the body and they override the heuristics.

Your tool → WardenPoint
alert-email.txtBASH
curl -X POST https://api.wardenpoint.com/api/v1/notifications/send \
-H "X-API-Key: $WARDENPOINT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"recipient_uuid": "00000000-0000-4000-8000-000000000001",
"message": "Custom service alert",
"priority": "critical",
"source": "custom"
}'
WardenPoint fan-out
WardenPoint response202
{
"status": "queued",
"notification_uuid": "notif_8h2k7yQrxJp",
"channels_planned": [
"telegram_voice",
"voice_call",
"email"
],
"escalation_chain_id": "esc_4j2k9bMcvL"
}

Routing recipes

Three patterns for email alerts

Run separate inboxes through separate integrations so each source gets its own routing, threshold and on-call group.

Legacy appliance with no webhook

A UPS, NAS or older monitor that only emails on fault. Point it at a per-device address and escalate to a phone call when nobody acknowledges.

PagerDuty / Opsgenie parity

Migrating off a tool that emailed a per-service alert address? Recreate the same flow here — one address per service, the same escalation behaviour, a fraction of the cost.

Deterministic alerts from your own jobs

A cron or script that emails on failure. Add severity: critical and dedup_key: backup-nightly to the body for exact severity and correlation, no guessing.

Email integration FAQ

Common email-to-alert questions

It is unguessable and acts as the capability key, but you should not rely on secrecy alone. Spam filtering runs in front of it, you can lock it to an allowlist of sender domains, and you can rotate the address from the dashboard at any time.
Free plan

Give your email alerts somewhere that calls back

Create an Email integration, send a test message to its address and watch it route through your escalation chain.

Start free Back to integrations
  • A unique address per source
  • Subject and body parsed into a routed alert
  • Rotate or lock the address anytime