Alert destination

PulseTrace + Microsoft Teams

Alerts in the Teams channel your team already watches.

Post PulseTrace alerts to a Microsoft Teams channel through an incoming webhook. Every event type — down, recovered, certificate expiring, grade change, anomaly — arrives as a message with the monitor, the failing regions and a link to the incident.

Set it up in three steps

1In Teams, open the channel → Manage channel → Connectors (or Workflows) and create an Incoming Webhook. Copy the URL.
2In PulseTrace, Settings → Developer & API → Webhooks → Add destination → type Microsoft Teams, paste the URL.
3Select the destination on the monitors that should alert it and send a test.

Events it receives

Monitor down / recovered
Still-down reminders
Certificate expiring
Security grade downgraded / recovered
Performance anomaly opened / closed
Significant external change (DNS, TLS, HTTP fingerprint, content)
Incident opened / acknowledged / resolved

Start monitoring free Read the docs

Teams card

Checkout API — DOWN
HTTP 503 · us-east, eu-west · started 14:02 UTC
Open incident #4821

Questions about Microsoft Teams

Which webhook should I create in Teams?

An incoming webhook for the channel. PulseTrace posts a simple JSON message to it; if your tenant has moved from Connectors to Workflows, use the Workflows "post to a channel when a webhook request is received" template and paste its URL.

Is the webhook URL stored securely?

Destination URLs are encrypted at rest and only ever shown masked after they are saved.

More alert destinations

SlackIncidents in the 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.