Connect PagerDuty so Coworker can answer incident and on-call questions. PagerDuty is indexed with one admin API key; individual users can additionally connect their own PagerDuty token so Coworker can act on incidents as them.
What Coworker can do with PagerDuty
Index incidents, lifecycle log entries, notes, services, teams, users, schedules, escalation policies and on-call shifts
Produce one reliability digest per service with incident activity: what fired, urgency, who responded, resolution state and notable patterns. Quiet services produce nothing.
Answer live questions on demand — what fired, who responded, who is on call now or over a window
Take incident actions on your behalf: create, acknowledge, resolve or snooze an incident, add a note, add a responder, override an on-call shift, or run a response play
Receive real-time updates through PagerDuty v3 webhooks on every incident transition
Services become Document entities and responders become Person entities anchored on email. Incidents, log entries, notes, shifts, schedules and escalation policies stay in the raw store and power the per-service reports.
Before you start
The workspace connection needs a PagerDuty account-level (admin) REST API key
US and EU PagerDuty accounts use different API hosts — the correct regional base URL is required even when the key itself is valid
To take write actions, you need your own PagerDuty User API token; PagerDuty records the acting user on every write
Connect as an admin
Open Data Sources from the admin settings in Coworker and select PagerDuty.
Paste your account-level REST API key.
Enter your regional API base URL (US or EU).
Save. Webhook subscriptions are registered automatically when the connection is created.
Use an account-level key rather than a narrowly scoped user token, so services, teams, schedules and incidents all share one organization view.
Connect as a member
Create a User API token in PagerDuty.
Go to the Work page and click Data Sources.
Select PagerDuty and paste your token.
Your personal token is what Coworker uses when you ask it to read or act on PagerDuty, so results and actions reflect your PagerDuty role.
Good to know
Incident data carries private access policies scoped to the people involved. Service metadata — names, descriptions, ownership — is indexed workspace-visible on purpose, because it is the low-sensitivity directory that makes on-call questions answerable.
Writes require an identified acting user. If your connection carries no user identity, write actions are refused with a reconnect message while reads keep working.
PagerDuty rate limits are enforced per account, so adding more keys improves resilience rather than raw throughput.
A restricted user's token returns silently filtered results on list endpoints, which is why discovery runs on the admin key.