Integrate PagerDuty with Round Robin

The PagerDuty integration lets Round Robin read your schedules and their participants. Connect it once per Slack workspace, then choose a schedule for each rotation.

You need: permission to manage workspace integrations and PagerDuty access to the schedules and users you want to use.

Choose a connection method

Method	What to prepare
API key	A PagerDuty API key with read access to schedules, teams and users. A read-only key is sufficient.
OAuth 2.0	A registered PagerDuty OAuth app, its client credentials and a PagerDuty user who can access the required schedules and users.

Both methods use the same schedule picker, including legacy and v3 schedules. Round Robin reads assignments from PagerDuty; it does not edit PagerDuty schedules or overrides.

Connect with an API key

1. Create a read-only API key in PagerDuty.
2. Open the Round Robin dashboard and go to workspace Settings → Integrations.
3. Click Connect on the PagerDuty card.
4. Paste the key into API Key and click Connect with API Key.

The card shows Connected and the last digits of the key. Use Edit API Key when you replace the credential.

Connect with OAuth 2.0

1. In PagerDuty, open Integrations → App Registration and create an app with OAuth 2.0 functionality.

2. Choose Scoped OAuth and register this redirect URL:

   https://api.roundrobinbot.eu/api/integrations/pagerduty/login/callback

3. Grant read access to Schedules, Teams and Users. Round Robin requests openid, schedules.read, teams.read and users.read.

4. Register the app and copy its Client ID and Client Secret.

5. In Round Robin, open workspace Settings → Integrations and click Connect on the PagerDuty card.

6. Enter OAuth Client ID and OAuth Client Secret, then click Connect with OAuth.

7. Authorize the connection in PagerDuty using an account that can access the schedules and users you need.

PagerDuty redirects you to Round Robin after authorization. Use Refresh Connection on the PagerDuty card to authorize again when access needs renewing.

Switch the connection method

Switching between OAuth and an API key keeps connected schedules, participant mappings, rotations and duty history. The current credentials remain in use until the replacement passes its access checks. The replacement must have access to every connected schedule, plus read access to schedules, teams and users.

Switch to an API key

1. Open workspace Settings → Integrations.
2. On the PagerDuty card, click Switch to API key.
3. Enter the replacement in API key, then click Switch to API key.

Authentication updated confirms the switch. The card shows the key’s last digits.

Switch to OAuth

1. On the PagerDuty card, click Switch to OAuth.
2. If an OAuth app is saved, leave Change OAuth app credentials unchecked to reuse it. To use another app, check it and enter OAuth client ID and OAuth client secret.
3. If no app is saved, register an OAuth app and enter its credentials. Use the Redirect URI shown in the dialog.
4. Click Continue to PagerDuty and authorize access to the account containing your connected schedules.

After authorization and access checks, the dashboard returns to Integrations with Authentication updated. Refresh Connection renews OAuth access using the saved app and the same checks.

Click Cancel before submitting to leave the connection unchanged. Cancelling authorization in PagerDuty also keeps the existing credentials. If a switch fails its access checks, correct the replacement credentials and try again.

Select a schedule

Connecting the integration does not choose a schedule for a rotation. Open that rotation’s Settings → Integrations → External schedule, choose PagerDuty, then select the schedule and click Connect this schedule.

See PagerDuty-based rotations to check participant mappings and read concurrent assignments in Coverage and Plan.

Restore access

Problem	What to check
Connect or Edit API Key is unavailable	Ask someone with permission to manage workspace integrations.
A schedule is missing from the picker	Check the search text and confirm that the connected key or OAuth user can access the schedule in PagerDuty.
Failed to load schedules. Please check your PagerDuty connection.	Check the credential on workspace Settings → Integrations. Replace the key with Edit API Key, or authorize again with Refresh Connection for OAuth.
Authentication update failed	Check the replacement credentials and their access to every connected schedule. The current connection is unchanged.
Connection changed	Refresh the page to check the current connection before retrying. Another connection or schedule change may have completed while the switch was in progress.
Authentication update not confirmed or Authorization not confirmed	Return to Integrations and refresh the page to check which connection method is active before retrying.
Authorization cancelled or Authorization expired	Click Back to integrations and start the switch again. Complete authorization within 15 minutes and use the latest attempt.
People appear without a Slack account	Check their email addresses or choose their Slack accounts on People & Groups. This is separate from the PagerDuty connection.

For Schedule data stale, Schedule unavailable and other assignment states, see Check a missing or outdated assignment.

Disconnect the integration

Use Disconnect to remove the integration. To replace its credentials while keeping rotations connected, switch the connection method.

On workspace Settings → Integrations, click Disconnect on the PagerDuty card and confirm.

This disconnects every rotation bound through the integration. Each returns to manual mode with no people and nobody on duty. Past duty history is kept. It does not change schedules in PagerDuty.

To disconnect one rotation while keeping the workspace connection, use that rotation’s settings. See Disconnect a rotation.

Next steps

• PagerDuty-based rotations: select a schedule and check its current and upcoming assignments.
• External rotations: map participants to Slack and manage an individual binding.