An Opsgenie Slack integration has two jobs: get Opsgenie alerts in front of the right people in Slack, and make it obvious who is on call right now. Opsgenie handles the first reasonably well on its own. The second - keeping Slack in step with your Opsgenie on-call schedules - is where most teams fall back on manual updates.

This guide covers how Opsgenie, Slack and Pagerly fit together, how to sync Opsgenie on-call schedules into Slack user groups, where Jira Service Management comes in, and how to set it up. For the product page, see Opsgenie and Slack 2-way sync.

Note: Atlassian is shutting Opsgenie down in April 2027. If you are planning the move, see the Opsgenie migration guide - Pagerly can import your Opsgenie schedules.

What Opsgenie, Slack and Pagerly Each Do

Opsgenie, an Atlassian product, covers:

On-call scheduling: rotations that make sure there is always a designated responder.
Alert management: aggregating alerts from monitoring tools and routing them to the right people.
Incident response coordination: integrations with ITSM tools, most deeply with Jira Service Management.

Slack is where the response actually happens: instant messaging for rapid response, and a hub for integrations so incident communication sits in one place.

Pagerly is the link between them. Its core job here is to keep Slack user groups, channel topics and mentions in sync with Opsgenie's on-call schedules - useful anywhere schedules change often.

What the Integration Gives You

Slack User Groups Synced with Opsgenie On-Call

Pagerly updates Slack user groups with the current on-call from your Opsgenie schedules, so a tag like @sre-on-call always reaches whoever is on call - no more manually adding and removing people at every handover.

Automated On-Call Handover Notifications

When the on-call changes, Pagerly notifies the team in Slack, and the user group follows automatically.

Mention the Current On-Call in Any Thread

Pagerly fetches the current on-call for each team so you can tag them in any Slack conversation, getting the question to the person who can answer it.

Channel Topic Updated with the Current On-Call

Pagerly updates team channel topics at every shift change, so everyone can see who is on call at a glance.

Group Multiple On-Calls

Mention several teams' on-call engineers at once - for example everyone on call for the frontend - with a single command, instead of looking each one up.

Manage and Override Schedules from Slack

See the Opsgenie schedule in Slack, and override the current on-call with any Slack user when someone needs cover.

Alerts and Tickets in Slack

Opsgenie alerts arrive in designated Slack channels or direct messages, where the team can acknowledge, escalate or resolve them. Pagerly also lets you create tickets straight from a Slack message and log them in Jira, Opsgenie or PagerDuty, keeping the discussion in the channel or thread.

Opsgenie, Slack and Jira Service Management

Opsgenie integrates deeply with Jira Service Management (JSM), so incidents handled in Opsgenie are logged and tracked in JSM. Put together, the flow runs from detection in Opsgenie, to communication in Slack, to tracking and resolution in JSM - which addresses the usual failure points of delayed response, disjointed communication and poor tracking. If you are weighing the two Atlassian tools, see Opsgenie vs Jira Service Management. For custom Jira, Opsgenie and JSM workflows over Slack, contact hello@pagerly.io.

How to Set Up the Opsgenie Slack Integration

Add Pagerly to Slack from pagerly.io. Some workspaces only let admins install apps.
Connect Opsgenie with an API key - see retrieving your Opsgenie API key or the Opsgenie API key guide.
Add the schedule you want to sync - see retrieving the schedule ID for Opsgenie.
Pick the Slack user group and channel that should follow the schedule. From then on, Opsgenie alerts and on-call changes show up in Slack, and the group tracks the rotation.

Before you start, make sure you have the right access in Opsgenie, Slack and Pagerly. See the developer documentation for full setup.

Troubleshooting

Most problems are connectivity or sync issues. Check that the Opsgenie API key has the permissions it needs, that account permissions are correct on each side, and that each Opsgenie user is matched to the right Slack account - an unmatched user breaks the sync for their shifts.

Best Practices

Check the sync periodically, especially after changing schedules or adding team members.
Use one user group per rotation, so it is always clear which team a mention reaches.
Use Slack's own tools during incidents - threads, pins and direct messages keep incident discussion easy to follow.

Conclusion

An Opsgenie Slack integration through Pagerly keeps Slack user groups, channel topics and mentions in step with your Opsgenie on-call schedules, and brings alerts and tickets into the channels where your team already works. The result is faster responses and less time spent maintaining who-is-on-call by hand.