Studio Project workflows for Atlassian Opsgenie alert routing, acknowledgment, and escalation
Atlassian OpsGenie is an alert and on-call management platform that routes, acknowledges, escalates, and manages alerts and incidents from monitoring and observability tools, backed by team-based on-call scheduling.
This project provides OpenAPI specs for automating against OpsGenie's REST API via an Integration Model. The -latest spec is a curated subset covering common CRUD for automation — see OpenAPIs below.
| Asset | Description |
|---|---|
| OpenAPIs/ | OpsGenie REST API OpenAPI specs — curated -latest plus the full dated spec |
| Studio Projects/Atlassian OpsGenie | 26 workflows covering common CRUD automation |
| Requirement | Version |
|---|---|
| Itential Platform | 6.x |
| Atlassian OpsGenie | API v2 (with legacy v1 endpoints for incidents/maintenance) |
| OpsGenie Integration Model | Required to build automation against the OpenAPI specs |
Import one of the OpenAPI specs from OpenAPIs/ as an Integration Model in Admin > Integrations, then create an integration pointing at your OpsGenie instance.
Authentication is an API key in the Authorization header, using the GenieKey scheme:
Authorization: GenieKey <your-opsgenie-api-key> Generate an API key in OpsGenie under Settings > API key management.
The instance's authentication/server properties should look like this once configured:
{
"authentication": {
"GenieKey": {
"value": "<your-genie-key>"
}
},
"server": {
"protocol": "https",
"host": "api.opsgenie.com",
"base_path": ""
}
} | Spec | Version | Operations | Description |
|---|---|---|---|
atlassian_opsgenie-latest.json | latest (curated) | 108 | Trimmed to 108 of 170 upstream operations — see breakdown below |
atlassian_opsgenie-2.0.0.json | 2.0.0 | 170 | Full, unmodified vendor spec |
atlassian_opsgenie-latest.jsonActively-maintained spec (x-vendor-api-version: 2.0.0). Trimmed to 108 of 170 upstream operations covering common CRUD for automation.
Resources included, by category:
Dropped as long-tail/admin: legacy v1 alert/notification policy endpoints (superseded by v2), saved searches, alert attachments, custom RBAC roles, per-team audit logs, calendar (.ics) exports, integration action/authenticate endpoints, and per-user personal admin (contact methods, personal notification rules and their steps, and per-user read-only lookups of teams/schedules/escalations/forwarding rules).
atlassian_opsgenie-2.0.0.jsonFull, unmodified vendor spec for OpsGenie API v2.0.0 (170 operations) — the vendor's complete API surface, preserved as-is. See atlassian_opsgenie-latest.json above for the curated subset if you just need common CRUD automation.
Backed by the Atlassian OpsGenie:latest Integration Model (see atlassian_opsgenie-latest.json above). The project contains 26 workflows organized into 5 folders, one atomic workflow per API operation, covering the common-CRUD subset of the curated spec.
| Folder | Workflows | Scope |
|---|---|---|
| Alerts | List, Create, Get, Delete, Acknowledge, Close Alert | Alert lifecycle |
| Teams | List, Create, Get, Update, Delete Team | Team lifecycle |
| Users | List, Create, Get, Update, Delete User | User lifecycle |
| Schedules | List, Create, Get, Update, Delete Schedule | On-call schedule lifecycle |
| Incidents | List, Create, Get, Delete, Close Incident | Incident lifecycle |
| Dependency | Notes |
|---|---|
Atlassian OpsGenie:latest Integration Model | Import from atlassian_opsgenie-latest.json before importing the project |
Atlassian OpsGenie integration instance | Create in Admin > Integrations with the connection properties above. Workflows are wired to an integration instance named Atlassian OpsGenie — update the adapter_id value in each workflow task if yours is named differently |