Skip to content
pulseback
Waitlist Join the waitlist
Docs menu

Email integration

Turn any email into an incident with an address of its own, and acknowledge or resolve alerts by replying to them.

Updated October 27, 2026

Some tools can only send email. Give them an address and every message becomes an alert. And when Pulseback emails you about an incident, you can act on it with a reply.

Email-to-incident

  1. In Integrations, add an Email integration and choose the escalation policy it pages and a default severity (sev3 unless you change it).
  2. Copy its address. It looks like:
<key>@alerts.pulseback.io
  1. Send alerts there from your monitoring tool, backup software, router or anything else that emails.

How messages are read:

  • The subject becomes the incident title.
  • Messages with the same subject are the same alert: Pulseback normalises the subject into a dedup key, so repeats are grouped into the open incident instead of paging again.
  • A subject that says the problem is over, such as one containing resolved or ok, resolves the matching incident.
  • The message body is attached to the alert.

If the address leaks, rotate the key from the integration’s settings; the old address stops working.

Acknowledge and resolve by replying

Every alert email Pulseback sends you has a reply address of its own (reply+<token>@alerts.pulseback.io), so you can act from your inbox:

Reply with (first line) What happens
ack Acknowledges the incident as you and stops escalation.
resolve Resolves the incident as you.
anything else Added to the incident timeline as a note from you.

Replies must come from the address the alert was sent to. Replies from anyone else are ignored, so a forwarded alert can’t be acknowledged by someone who isn’t on the incident.

Tips

  • Use one email integration per sending system, so you can see where an alert came from and rotate keys independently.
  • If your tool lets you template subjects, put the stable part first (“Backup failed: db-1”) and leave timestamps out, so repeats group.
  • For anything that can make HTTP requests, the Events API gives you explicit dedup keys and severities.