Skip to content

PagerDuty and OpsGenie based rotations

You can link a Round Robin rotation to a PagerDuty or OpsGenie schedule. The rotation’s members and the user on duty are then sourced directly from the external schedule instead of being managed in Round Robin.

This lets you keep using all of Round Robin’s Slack features — the on-duty group, topics, templates, mentions — without maintaining the same shift plan in two places.

This page uses PagerDuty in the examples; everything applies to OpsGenie as well.

Say you have a PagerDuty schedule called Service X that manages the on-call duty for a service in your organization.

A PagerDuty schedule named Service X

Everything happens in the dashboard:

  1. Create a rotation as usual (the name does not have to match the schedule). Don’t bother adding members — they will be managed automatically. You can still configure channels, topics, and other options.

    The Create Rotation page in the dashboard, with the Details tab filled in

  2. Open the rotation’s page and go to its Schedule section.

    A rotation page in the dashboard, showing the summary cards and the Schedule section

  3. Under Schedule Type, pick PagerDuty (or OpsGenie) in the External group. These options only appear when the integration is connected.

  4. Search for the schedule by name and select it, then save.

The rotation is now externally managed.

After the first sync:

  • The rotation’s members are replaced with the schedule’s members.
  • Whoever is currently on call in the schedule goes on duty in Round Robin.
  • When the schedule changes (new members, removed members, a different person on call), the rotation follows.

The sync runs periodically — roughly once a minute — so changes are not reflected in real time.

Users are matched by email address: Round Robin looks up each schedule member’s email in your Slack workspace. The rotation’s Users panel in the dashboard shows how many schedule members are linked to Slack. If someone is on call but their email does not match any Slack user, Round Robin tracks them as an unmapped external user and shows their name from the external service instead.

Setting Editable while linked?
Members and groups No — the on-call pool is owned by the external schedule and is overwritten on every sync
Schedule type and timing No — the external schedule drives all transitions
Channels, topics, templates, on-duty group, other options Yes — managed in Round Robin as usual

To unlink a rotation, open its Schedule section in the dashboard and click Disconnect external schedule. The rotation switches back to manual mode, and the members last synced from the schedule are kept as the starting pool. You can re-link an external schedule at any time.

Disconnecting the PagerDuty or OpsGenie integration itself (in Settings → Integrations) reverts all bound rotations to manual mode at once.

In Slack, an externally managed rotation’s description shows the external mode:

Slack rotation card showing Rotation Mode: PagerDuty (external)