PagerDuty

Manage incidents, schedules, and on-call rotations with PagerDuty.

Detail	Value
Category	Dev Tools
Base URL	https://api.pagerduty.com
Authentication	Bearer Token
Endpoints	6
Connector key	pagerduty

Using PagerDuty in a workflow

1. Go to Connections and click New Connection.
2. Pick PagerDuty 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 /incidents	List incidents
POST /incidents	Create an incident
GET /incidents/{id}	Get an incident
PUT /incidents/{id}	Update an incident
GET /services	List services
GET /oncalls	List on-call entries

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

GET /incidents

List incidents

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

Parameters

Name	Location	Type	Required
statuses[]	query	string	No
since	query	string	No
until	query	string	No

Using this endpoint in a workflow

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

POST /incidents

Create an incident

Detail	Value
Operation ID	devtools.createIncident
Method	POST
Path	/incidents

Parameters

No parameters.

Request Body

Field	Type
incident	object

Using this endpoint in a workflow

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

Required fields are marked — fill them or the call will fail at runtime.

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.

GET /incidents/{id}

Get an incident

Detail	Value
Operation ID	devtools.getIncident
Method	GET
Path	/incidents/{id}

Parameters

Name	Location	Type	Required
id	path	string	Yes

Using this endpoint in a workflow

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

Required fields are marked — fill them or the call will fail at runtime.

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.

PUT /incidents/{id}

Update an incident

Detail	Value
Operation ID	devtools.updateIncident
Method	PUT
Path	/incidents/{id}

Parameters

Name	Location	Type	Required
id	path	string	Yes

Request Body

Field	Type
incident	object

Using this endpoint in a workflow

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

Required fields are marked — fill them or the call will fail at runtime.

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.

GET /services

List services

Detail	Value
Operation ID	devtools.listServices
Method	GET
Path	/services

Parameters

No parameters.

Using this endpoint in a workflow

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

GET /oncalls

List on-call entries

Detail	Value
Operation ID	devtools.listOnCalls
Method	GET
Path	/oncalls

Parameters

Name	Location	Type	Required
schedule_ids[]	query	string	No

Using this endpoint in a workflow

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