Issues & support
Set up PagerDuty
Connect PagerDuty to make incident history searchable — each service and each incident becomes a document with status, urgency, priority, who was assigned and the responders' notes, tied to its service and teams, so “have we seen this outage before” and “who handled it last time” answer from the pager log itself. Read-only.
Before you start
- PagerDuty → Integrations → API Access Keys → Create New API Key — a general access REST API key with Read-only access ticked; nothing else is used.
- The key sees every service, incident and user on the account. Only reads are ever issued.
- US-hosted PagerDuty accounts only for now — the EU service region has its own API address, which this connector doesn't reach.
- Documents → PagerDuty, paste the REST API key.
- Teams (Advanced): optional team ids or exact names, one per line — blank syncs every team's services and incidents.
- Choose access groups, Test, then Sync.
| Teams | Limits the sync to certain teams: a team id (the PXXXXXX code in its URL) or its exact name, one per line. Names are looked up once per sync; an entry that matches nothing is reported and ignored. Blank syncs the whole account. |
|---|
What comes in
- Each service becomes a document — status, escalation policy, teams, the date of its last incident, a link back, and its description — the closest thing to a standing runbook note.
- Each incident becomes a document titled with its number and title — status, urgency, priority, service, who it was assigned to, when it opened and last changed, a link back, and the responders' notes, each with who wrote it and when. Resolved incidents are the record and sync too.
- Notes are read for incidents that are new or have changed. A note added on its own, with nothing else changing, may not appear until the incident next changes its status, priority or assignee.
Access
Services and incidents follow their teams' members: everyone PagerDuty lists on a team, by email, becomes a viewer of that team's services and incidents, re-checked on every sync. One with no team, or whose team's members can't be resolved, keeps this source's access groups instead; when the user directory can't be read at all, Sync says so and everything keeps the source's groups. Access stays allow-only either way. Switch How access works to “One list for everything” under Permissions to put everything this source brings in under the chosen access groups instead.
Caps: 300 services and the 1,000 most recent incidents per sync, newest first — Sync notes a cap it hits, and services and incidents already synced stay searchable past it. Test lists the first services the key can see; it fails with a specific reason when PagerDuty rejects the key. Revoke access any time by deleting the key under Integrations → API Access Keys.
Last updated 20 Sep 2026