Statuspage

Manage status pages, components, incidents, and subscribers with Atlassian Statuspage.

Detail	Value
Category	Monitoring
Base URL	https://api.statuspage.io/v1
Authentication	API Key
Endpoints	8
Connector key	statuspage

Using Statuspage in a workflow

1. Go to Connections and click New Connection.
2. Pick Statuspage 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 /pages	List pages
GET /pages/{page_id}	Get page details
GET /pages/{page_id}/components	List components
POST /pages/{page_id}/components	Create a component
GET /pages/{page_id}/incidents	List incidents
POST /pages/{page_id}/incidents	Create an incident
GET /pages/{page_id}/incidents/unresolved	List unresolved incidents
GET /pages/{page_id}/subscribers	List subscribers

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

GET /pages

List pages

Detail	Value
Operation ID	monitoring.listPages
Method	GET
Path	/pages

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Statuspage connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listPages.
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 Statuspage API reference.

GET /pages/{page_id}

Get page details

Detail	Value
Operation ID	monitoring.getPage
Method	GET
Path	/pages/{page_id}

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Statuspage connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.getPage.
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 Statuspage API reference.

GET /pages/{page_id}/components

List components

Detail	Value
Operation ID	monitoring.listComponents
Method	GET
Path	/pages/{page_id}/components

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Statuspage connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listComponents.
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 Statuspage API reference.

POST /pages/{page_id}/components

Create a component

Detail	Value
Operation ID	monitoring.createComponent
Method	POST
Path	/pages/{page_id}/components

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Statuspage connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.createComponent.
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 Statuspage API reference.

GET /pages/{page_id}/incidents

List incidents

Detail	Value
Operation ID	monitoring.listIncidents
Method	GET
Path	/pages/{page_id}/incidents

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Statuspage 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 Statuspage API reference.

POST /pages/{page_id}/incidents

Create an incident

Detail	Value
Operation ID	monitoring.createIncident
Method	POST
Path	/pages/{page_id}/incidents

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Statuspage connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.createIncident.
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 Statuspage API reference.

GET /pages/{page_id}/incidents/unresolved

List unresolved incidents

Detail	Value
Operation ID	monitoring.listUnresolvedIncidents
Method	GET
Path	/pages/{page_id}/incidents/unresolved

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Statuspage connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listUnresolvedIncidents.
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 Statuspage API reference.

GET /pages/{page_id}/subscribers

List subscribers

Detail	Value
Operation ID	monitoring.listSubscribers
Method	GET
Path	/pages/{page_id}/subscribers

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Statuspage connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listSubscribers.
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 Statuspage API reference.