On-call
PagerDuty
Two-way incident sync with PagerDuty: incidents created or resolved in either system update the other, plus a cached read of on-call schedules for scheduling awareness.
BidirectionalData residency: US
Request a demoWhat it does
- incident.trigger and incident.resolve keep a linked PagerDuty incident and platform incident in step (bidirectional)
- On-call schedule cache polled on a 60-second default cadence
- Outbound: fires the PagerDuty Events API v2 on qualifying incidents
- Health check validates the stored API token against PagerDuty's lightweight /abilities endpoint
- Architecturally extensible to Opsgenie via a parallel adapter sharing the same sync pattern — not shipped yet
Data residency
PagerDuty is a US-based SaaS; enabling this integration requires the tenant's explicit data-residency acknowledgement.
Event mappings
| External event | Maps to | What happens |
|---|---|---|
| incident.trigger | incident | PagerDuty incident trigger creates or links a platform incident |
| incident.resolve | incident | PagerDuty incident resolve updates platform incident state |
What you configure
- API token (stored as a secret; validated against PagerDuty's abilities endpoint)
OAuth scopes requested
- read
- write
Setup overview
Store a PagerDuty REST API token as a secret — PagerDuty itself authenticates with a static token, not an interactive OAuth grant. The health probe calls PagerDuty's /abilities endpoint to confirm the token is valid before enabling sync.
Related features
See TENSOR running on your own estate.
30 minutes, screen-shared, no slides. Bring the process you are least sure we handle and we will start there.