Integrations / PagerDuty

PagerDuty notifications in Microsoft Teams

PagerDuty incidents in Teams — triggered, acknowledged, and resolved, in the channel. Per My Last Webhook normalizes PagerDuty events into rich Adaptive Cards and posts them to a Teams channel, a person's DM, or a webhook — the successor to Office 365 Connectors.

How it works

  1. PagerDuty POSTs a webhook to your private ingest URL when a build runs.
  2. We normalize it — the same card format as every other platform.
  3. The card lands in your chosen Teams destination, with routing and noise controls applied.

Set up in minutes

Create a subscription in the app (platform: PagerDuty), copy its ingest URL, then:

1

Create a subscription (platform PagerDuty) and copy its ingest URL.

2

PagerDuty → Integrations → Generic Webhooks (v3) → New Webhook.

3

Set the Webhook URL to your ingest URL and subscribe to incident events — the v3 payload is normalized as-is.

4

Trigger a test incident → the card lands.

See it instantly

Don't want to wait for a build? Hit Test on the subscription — a card lands immediately. Full steps in the platform reference.

What lands in Teams

Teams · #ci
🔴 Database down · failure
PagerDuty · prod · alice · 3m 20s

Built for teams, not just alerts

Routing PRO

Prod failures to #prod-alerts, the rest to #ci.

Incident mode PRO

Collapse a flapping pipeline into one updating card.

On-call DMs PRO

DM the owner the moment their PagerDuty build breaks.

Status filters

Only care about failures? Filter to just those — free.

Part of Per My Last Webhook — all 17 integrations into one Teams app.

▣ StartPER MY LAST WEBHOOKC:\INTEGRATIONS\PAGERDUTYStatus: 200 OK