Opsgenie
Connect Opsgenie to Ploy to see every user in your Opsgenie account, their account role, whether they are blocked, which teams they belong to, and who is on call on each schedule right now. Ploy can also add people to the account, change their account role, remove them, and add or remove them from teams.
This integration is in beta
The Opsgenie integration is in beta. It was built from Opsgenie's API documentation and has not yet been checked against a live Opsgenie account, so some details may need adjusting once customers connect it. Beta does not limit what the integration can do.
The first step of setup is a consent checkbox. Ticking it lets Ploy capture redacted error data when a request to Opsgenie fails: the error response Opsgenie sends back, with personal details, keys and other secrets removed. Ploy uses it only to fix problems with this integration. You must tick the box to continue.
What Ploy reads
Every user in your Opsgenie account, with their name and email address
Each user's account role: Owner, Admin, User, Stakeholder, or one of your custom roles
Whether each user is blocked
Every team, and the members of each team, including who is a team admin
Every on-call schedule, and who is on call on it right now (people reached through an escalation are included)
Ploy does not read your alerts, incidents, heartbeats or notification rules.
Before you start
You need to be an Opsgenie Owner or Admin to manage API integrations.
Know which region your account is hosted in: the United States (the default) or the European Union. If your Opsgenie address ends in eu.opsgenie.com, choose the European Union.
Use an API integration that is not assigned to a team. A team API integration cannot read or change team membership.
Create an API key in Opsgenie
Sign in to Opsgenie as an Owner or Admin.
Open Settings, then Integrations.
Add a new API integration (or open the existing Default API integration). Give it a name such as Ploy.
Leave it unassigned to any team.
Turn on Read access. Turn on Create and Update access and Delete access too if you want Ploy to add, change and remove people. Ploy does not need configuration access.
Save the integration, make sure it is turned on, and copy its API key. Treat it like a password.
Connect Opsgenie in Ploy
In Ploy, open Integrations and choose Opsgenie.
Tick the beta consent checkbox.
Select your Opsgenie region.
Paste the API key.
Click Test. Ploy reads your Opsgenie users to check the key and region work.
Finish the setup. The first scan starts straight away.
Things to know
Users are checked every hour, along with who is on call. Teams and their members are checked every six hours.
A blocked user shows as inactive in Ploy and loses their access.
People who have not yet confirmed their email address still count as users with access.
Adding a person creates them with the User role and Opsgenie sends them an invitation email. Someone who already has an Opsgenie user is left as they are.
Removing a person deletes their Opsgenie user, which also takes them off every team and schedule. This cannot be undone from Ploy.
Ploy cannot block or unblock users, and cannot make someone the account owner.
Adding someone to a team from Ploy makes them a team member, not a team admin. They must already be an Opsgenie user.
Troubleshooting
Opsgenie refused the API key
Check the key was copied in full, that its API integration is still turned on in Opsgenie, and that the region you chose matches your account. A key only works in its own region.
Opsgenie refused to list users
The API integration needs Read access. Check it is not assigned to a team.
A change from Ploy was refused
The API integration needs Create and Update access to add people and change roles, and Delete access to remove people. Opsgenie's own reason is shown with the error.