Alert destination

PulseTrace + Rootly

Rootly alerts from PulseTrace monitors.

When PulseTrace opens an incident, it creates a matching incident in Rootly so Rootly's workflows — Slack channel, roles, timeline, retrospective — start from the monitoring signal.

Set it up in three steps

1In Rootly, create an API key with permission to create incidents.
2In PulseTrace, add a destination of type Rootly and paste the key.
3Enable the "New incident opened" event on the destination; each PulseTrace incident creates one Rootly incident with the summary and a link back.

Events it receives

Incident opened (creates a Rootly incident)

Start monitoring free Read the docs

Rootly 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 Rootly

Is the API key stored safely?

Yes — like every destination credential, it is encrypted at rest and shown masked after saving.

More alert destinations

SlackIncidents in the channel your team already watches.Microsoft TeamsAlerts in the Teams channel your team already watches.DiscordAlerts for the Discord-first team.TelegramA bot message the moment something drifts.PagerDutyTrigger and auto-resolve PagerDuty incidents.OpsgenieOpen and close Opsgenie alerts automatically.