Integrations

Every alert, where your team already is.

Ten alert destinations and four developer surfaces, all fed by the same incident timeline — so Slack, PagerDuty and your own webhook always tell the same story.

Alert destinations

Where incidents, recoveries and warnings are delivered.

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.incident.ioDeclare incidents in incident.io from monitor failures.RootlyRootly alerts from PulseTrace monitors.EmailPlain, reliable email alerts — on every plan.WebhooksA signed JSON webhook for anything else you run.

Developer surfaces

How code, agents and your own infrastructure talk to PulseTrace.

MCP serverLet Claude, Cursor and your own agents run your monitoring.REST APIEverything the dashboard does, as JSON.OpenAPI importTurn a spec into a monitor per endpoint.Probe agentCheck from inside your own network.

Missing one? Use the webhook.

A signed JSON payload for every event reaches anything with an HTTPS endpoint — automation platforms, ticketing, chatops, your own services.

Start monitoring free Webhook reference