GET /incidents ​
List incidents
| Detail | Value |
|---|---|
| Operation ID | devtools.listIncidents |
| Method | GET |
| Path | /incidents |
| Connector | PagerDuty |
Parameters ​
| Name | Location | Type | Required |
|---|---|---|---|
statuses[] | query | string | No |
since | query | string | No |
until | query | string | No |
Using this endpoint in a workflow ​
- Add an API Call node to your workflow.
- Pick your PagerDuty connection from the Connection dropdown.
- In the Operation dropdown, select
devtools.listIncidents. - 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 PagerDuty API reference.