Incidents in the channel your team already watches.
Connect Slack with one click and route PulseTrace alerts to any channel. Down, recovered, certificate expiry and security-grade changes arrive as rich messages with a link back to the incident.
Set it up in three steps
1Open Settings → Developer & API → Slack and click Connect Slack. PulseTrace uses a platform-level Slack app, so there are no client IDs or secrets to paste — you sign in to Slack and approve the workspace.
2Pick the channel (or channels) that should receive alerts. Private channels work once the PulseTrace bot is invited.
3In any monitor's Alerting tab, tick the Slack destination. Use a test send to confirm the message lands.
🔴 Checkout API is DOWN
HTTP 503 from us-east, eu-west (2 of 3 regions)
Started 14:02 UTC · Incident #4821 · 3 checks failed
View incident → https://app.pulsetrace.app/dashboard/incidents/4821
Questions about Slack
Do I need to create a Slack app?
No. Slack is connected at the platform level, so an organization owner or admin only has to click Connect Slack and approve the workspace. Legacy incoming-webhook URLs are still accepted as a separate destination type if you prefer them.
Can different monitors post to different channels?
Yes. Each channel is its own destination, and every monitor chooses which destinations it alerts, so production can page #incidents while staging goes to #staging-noise.
Does recovery post too?
Yes — a recovered message references the original alert, and still-down reminders repeat on the interval you configure per monitor.