Email ingest

Send Mailgun alert e-mail to on-call with CallHeim.

Forward Mailgun alert e-mail to your organization’s inbound alert address and each message becomes an alert (Trial, Business and Enterprise plans). CallHeim maps the payload, attaches repeats to the incident that is already open, and pages whoever is on call for the service it belongs to.

mailgunsource names also accepted: mailgun-inbound, mg

Setting it up

Send Mailgun alert mail to your organization’s inbound alert address, shown on your e-mail integration in CallHeim. The subject becomes the alert title, and a repeat with the same subject attaches to the open incident if that incident was triggered in the last 24 hours.

If you already forward Mailgun mail somewhere that can POST JSON, the generic webhook takes it too.

Mailgun documentation →

Setup snippetmailgun
# Forward Mailgun alert mail to your organization’s inbound alert address (your e-mail integration in CallHeim).
# Available on the Trial, Business and Enterprise plans.
Check Mailgun’s current documentation for the exact fields.

After it arrives

What CallHeim does with Mailgun alerts.

Some tools only send mail. Each organization on the Trial, Business and Enterprise plans (not Starter or Pro) gets its own inbound alert e-mail address for email-to-alert; mail sent to it becomes an alert with the same fingerprint, dedup and severity treatment as a webhook. The identity is the e-mail subject, so a repeat joins an open incident only if it was triggered in the last 24 hours. On plans with email-to-alert, e-mail rules filter incoming mail and decide what opens or resolves an incident from the subject, sender or body.

CallHeim reads a [P1]-style tag or the word CRITICAL in the subject as the severity, and shows a separate, explainable severity suggestion that a person can apply. How severity is suggested →

Each alert source is bound to a service, and the service’s escalation policy (or its team’s) sets who is paged. Alerting and escalation →

The thresholds it passes through

Repeat, sender-supplied dedup key
attaches, any age
Repeat, title or subject only
attaches, incident under 24 h old
Flap threshold
4 transitions / 600s
Title correlation
similarity ≥ 0.6, same source and service
Group window default
600s

All defaults are published. You can turn title correlation off or change its threshold, and set the window on your own noise rules; the dedup rule and the flap settings are fixed. A P1 or P2 repeat on an open P3 to P5 incident opens a new incident and pages. How alerts are processed →

CallHeim

Point Mailgun at CallHeim and see what it does with your alerts.

Start on the free trial, connect Mailgun and send a test alert to see the incident it opens.