Opsgenie

Manage alerts, incidents, on-call schedules, and teams with Atlassian Opsgenie.

Detail	Value
Category	Monitoring
Base URL	https://api.opsgenie.com/v2
Authentication	API Key
Endpoints	8
Connector key	opsgenie

Using Opsgenie in a workflow

1. Go to Connections and click New Connection.
2. Pick Opsgenie from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET /alerts	List alerts
POST /alerts	Create an alert
GET /alerts/{identifier}	Get alert details
POST /alerts/{identifier}/acknowledge	Acknowledge an alert
POST /alerts/{identifier}/close	Close an alert
GET /incidents	List incidents
GET /schedules	List on-call schedules
GET /teams	List teams

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /alerts

List alerts

Detail	Value
Operation ID	monitoring.listAlerts
Method	GET
Path	/alerts

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Opsgenie connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listAlerts.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Opsgenie API reference.

POST /alerts

Create an alert

Detail	Value
Operation ID	monitoring.createAlert
Method	POST
Path	/alerts

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Opsgenie connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.createAlert.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Opsgenie API reference.

GET /alerts/{identifier}

Get alert details

Detail	Value
Operation ID	monitoring.getAlert
Method	GET
Path	/alerts/{identifier}

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Opsgenie connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.getAlert.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Opsgenie API reference.

POST /alerts/{identifier}/acknowledge

Acknowledge an alert

Detail	Value
Operation ID	monitoring.acknowledgeAlert
Method	POST
Path	/alerts/{identifier}/acknowledge

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Opsgenie connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.acknowledgeAlert.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Opsgenie API reference.

POST /alerts/{identifier}/close

Close an alert

Detail	Value
Operation ID	monitoring.closeAlert
Method	POST
Path	/alerts/{identifier}/close

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Opsgenie connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.closeAlert.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Opsgenie API reference.

GET /incidents

List incidents

Detail	Value
Operation ID	monitoring.listIncidents
Method	GET
Path	/incidents

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Opsgenie connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listIncidents.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Opsgenie API reference.

GET /schedules

List on-call schedules

Detail	Value
Operation ID	monitoring.listSchedules
Method	GET
Path	/schedules

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Opsgenie connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listSchedules.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Opsgenie API reference.

GET /teams

List teams

Detail	Value
Operation ID	monitoring.listTeams
Method	GET
Path	/teams

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Opsgenie connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listTeams.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Opsgenie API reference.