All integrations
Alert destination

PulseTrace + incident.io

Declare incidents in incident.io from monitor failures.

When PulseTrace opens an incident, it declares a matching incident in incident.io with the severity you choose — so your incident process, roles and Slack channels start from the monitoring signal without anyone re-typing it.

Set it up in three steps

  1. 1In incident.io, note the severity you want PulseTrace incidents to open with (its severity ID) and create an API key with incident-creation permission.
  2. 2In PulseTrace, add a destination of type incident.io with the API endpoint/key and the severity ID.
  3. 3Enable the "New incident opened" event on that destination. Each PulseTrace incident then creates one incident.io incident with the summary and a link back.

Events it receives

  • Incident opened (creates an incident.io incident)
incident.io incident
Checkout API is DOWN
HTTP 503 from us-east, eu-west (2 of 3 regions)
PulseTrace incident #4821 → https://app.pulsetrace.app/dashboard/incidents/4821

Questions about incident.io

Does PulseTrace close the incident.io incident on recovery?
No — incident.io incidents are run by people, so PulseTrace opens them and your team closes them; the PulseTrace incident is linked so its own timeline shows the recovery.