Integrations

PagerDuty

Add, use, and remove the PagerDuty OAuth integration for paging workflows.

PagerDuty OAuth Integration

PagerDuty is supported as a Paging provider.

Prerequisites

  • You are a workspace admin in RectifAI.
  • The connected PagerDuty account can read services, schedules, escalation policies, and incidents.
  • If you enable webhook sync, your PagerDuty account can create webhook subscriptions.
  • PagerDuty is set as the default paging provider if you want operational paging automation to use it.

Add the PagerDuty integration

  1. Open Workspace -> Integrations -> Paging -> PagerDuty.
  2. Click Connect PagerDuty.
  3. Sign in to PagerDuty if prompted.
  4. Choose the PagerDuty account and approve access.
  5. Return to RectifAI and confirm the integration shows as connected.
  6. Review available services and escalation policies.
  7. Set PagerDuty as the default Paging provider if that is how your workspace handles on-call response.
  8. If you want account-wide inbound event sync, enable the optional PagerDuty webhook subscription from the PagerDuty integration page.

Use PagerDuty in RectifAI

  • Map systems and teams to PagerDuty services or escalation policies.
  • Trigger or correlate paging workflows during incidents.
  • Bring PagerDuty incident context into RectifAI.
  • Optionally sync PagerDuty webhook events back into the workspace.

Remove the PagerDuty integration

  1. Open Workspace -> Integrations -> Paging -> PagerDuty.
  2. Click Disconnect.
  3. Confirm the provider now shows as not connected.
  4. If you enabled a PagerDuty webhook subscription, remove or disable it in PagerDuty as well if your team wants the external subscription cleaned up immediately.

What happens after removal

  • RectifAI stops using PagerDuty for new paging workflows in that workspace.
  • PagerDuty service and escalation policy data can no longer be refreshed.
  • Any PagerDuty incidents or webhook subscriptions already created in PagerDuty are not automatically removed.

Data handling

  • RectifAI removes the stored PagerDuty OAuth tokens for the workspace.
  • Historical incident records stored in RectifAI remain under the normal retention policy.
  • PagerDuty-side incidents, services, or webhook subscriptions remain in PagerDuty unless removed there.

Troubleshooting

If you run into trouble during setup or removal, see the Troubleshooting guide.