PagerDuty

PagerDuty connects with a REST API key — there's no OAuth flow to walk through the way Jira has.

What it unlocks

The On-Call Registry — its own section in the main sidebar, not part of Reports — needs a PagerDuty connection; every report works without one.

Connecting

Generate a read-only API key from PagerDuty (Settings → API Access → Create New API Key), then paste it into Settings → Integrations → PagerDuty. There's no per-schedule picker to configure afterward — every current on-call assignment across your PagerDuty account syncs automatically, on a 30-minute backstop poll plus a push whenever PagerDuty reports an incident event.

How a schedule maps to a team

There's no separate "map this schedule to that team" step. Vertly matches each PagerDuty user to a person by email — the same matching it already does for Jira — and a team's on-call entry is simply whichever of that team's members currently shows up as on-call. If the automatic email match picks the wrong person (common when someone uses a different email address in PagerDuty than in GitHub or Jira), correct it from Settings → Teams: unlink the PagerDuty identity from the wrong person and link it to the right one. The correction sticks — it's never silently re-matched away by a later sync.

Credential handling

PagerDuty API keys are stored encrypted, scoped to your org, and stop being used the moment you disconnect the integration from Settings.