PagerDuty actions

This page provides a comprehensive reference for PagerDuty actions available in the workflow automation actions catalog. These actions enable you to integrate PagerDuty incident management into your workflow definitions, including creating, updating, resolving, listing, and retrieving incidents.

Prerequisites

Before using PagerDuty actions in workflow automation, ensure you have:

A PagerDuty account with appropriate permissions.
A PagerDuty API token (either a user token or account token).
The necessary permissions to manage incidents in your PagerDuty account.
For account tokens, you'll need to provide the from email address in relevant actions.

Incident actions

Resolves a PagerDuty incident by updating its status to resolved with optional resolution notes.

Input Field	Optionality	Type	Example
token	Required	String	`${{ :secrets:pagerdutyApiToken }}`
incidentId	Required	String	`1234567`
type	Required	String	`“incident“`
from	Optional	String	`test@example.com` The `from` field is required for account tokens but optional for user tokens
resolution	Optional	String	`“System is up and running and incident is resolved”`
selectors	Optional	List	`[name: incidentId ,expression: .responseBody \| fromjson.incident.id]`

Output Field	Type	Example
response	object	`{ "incident": { "incident_number": 1233456, "title": "Example incident title1", "description": "Example incident title1", "created_at": "2025-10-14T05:30:30Z", "updated_at": "2025-10-14T05:58:53Z", "status": "resolved", .... } }`
success	Boolean	`success: true \| false`
errorMessage	String	`{\"incident\":{\"errors\":[\"Incident Already Resolved\"],\"id\":\"Q2TJNU161RMNBO\",\"type\":\"incident_reference\",\"summary\":\"[#4212416] Example incident`

Workflow example
`name: resolve-pagerduty-incident description: '' steps: - name: pagerduty_incident_resolve_1 type: action action: pagerduty.incident.resolve version: 1 inputs: token: ${{ :secrets:pagerdutyApiToken }} from: abc@example.com type: incident incidentId: Q1234567890 resolution: The incident is resolved and not action is needed next: end`

Workflow example

name: resolve-pagerduty-incident
description: ''
steps:
  - name: pagerduty_incident_resolve_1
    type: action
    action: pagerduty.incident.resolve
    version: 1
    inputs:
      token: ${{ :secrets:pagerdutyApiToken }}
      from: abc@example.com
      type: incident
      incidentId: Q1234567890
      resolution: The incident is resolved and not action is needed
    next: end

Retrieves a list of incidents from PagerDuty with optional filtering parameters such as date ranges and status.

Input Field	Optionality	Type	Example
token	Required	String	`${{ :secrets:pagerdutyApiToken }}`
parameters	Optional	Map	`{ offset: 0 , incident_key: 1234-5678-0101123 }`
selectors	Optional	List	`[name: incidentId ,expression: .responseBody \| fromjson.incident.id]`

Importante

The PagerDuty List API supports multiple optional query parameters, which can be efficiently handled using a parameter map

Output Field	Type	Example
response	object	`{ “incidents”: [ { “incident_number”: 1234, “title”: “Test Incident 1" ... } ] }`
success	Boolean	`success: true \| false`
errorMessage	String	`"error": { "message": "The request took too long to process.", "code": 2016 }`

Workflow example
`name: list-pagerduty-incidents description: '' steps: - name: pagerduty_incident_list_1 type: action action: pagerduty.incident.list version: 1 inputs: token: ${{ :secrets:pagerdutyApiToken }} parameters: since: '2025-10-14T10:30:00Z' statuses[]: 'resolved' next: end`

Workflow example

name: list-pagerduty-incidents
description: ''
steps:
  - name: pagerduty_incident_list_1
    type: action
    action: pagerduty.incident.list
    version: 1
    inputs:
      token: ${{ :secrets:pagerdutyApiToken }}
      parameters:
        since: '2025-10-14T10:30:00Z'
        statuses[]: 'resolved'
    next: end

Retrieves detailed information about a specific PagerDuty incident by its ID.

Input Field	Optionality	Type	Example
token	Required	String	`${{ :secrets:pagerdutyApiToken }}`
incidentId	Required	String	`Q123456789`
parameters	Optional	Map	`{ include[] : “services“ }`
selectors	Optional	List	`[name: incidentId ,expression: .responseBody \| fromjson.incident.id]`

Output Field	Type	Example
response	Object	`{ “incidents”: [ { “incident_number”: 1234, “title”: “Test Incident 1" ... } ] }`
success	Boolean	`success: true \| false`
errorMessage	String	`"error": { "message": "The request took too long to process.", "code": 2016 }`

Workflow example
`name: get-pagerduty-incident description: '' steps: - name: pagerduty_incident_get_1 type: action action: pagerduty.incident.get version: 1 inputs: token: ${{ :secrets:pagerdutyApiToken }} incidentId: Q1234455677 next: end`

Workflow example

name: get-pagerduty-incident
description: ''
steps:
  - name: pagerduty_incident_get_1
    type: action
    action: pagerduty.incident.get
    version: 1
    inputs:
      token: ${{ :secrets:pagerdutyApiToken }}
      incidentId: Q1234455677
    next: end

Creates a new incident in PagerDuty with specified service, title, priority, and other optional attributes.

Input Field	Optionality	Type	Example
token	Required	String	`${{ :secrets:pagerdutyApiToken }}`
type	Required	String	`“Incident“`
title	Required	String	`“Test Incident“`
service	Required	Map	`"service": { "id": "PV5L94Z", "type": "service_reference" }`
from	Optional	String	`abc@example.com` The from field is required for account tokens but optional for user tokens
priority	Optional	Map	`"priority": { "id": "P53ZZH5", "type": "priority_reference" }`
urgency	Optional	String	`"Low"`
body	Optional	Map	`"body": { "type": "incident_body", "details": "A disk is getting full on this machine. You should investigate what is causing the disk to fill, and ensure that there is an automated process in place for ensuring data is rotated (eg. logs should have logrotate around them). If data is expected to stay on this disk forever, you should start planning to scale up to a larger disk." }`
incidentKey	Optional	String	`1234-5678-919123`
assignments	Optional	List	`[ { "assignee": { "id": "P11223", "type": "user_reference" } } ]`
incidentType	Optional	String	`"incident_type": { "name": "major_incident" }`
escalationPolicy	Optional	Map	`"escalation_policy": { "id": "PT20YPA", "type": "escalation_policy_reference" }`
conferenceBridge	Optional	Map	`"conference_bridge": { "conference_number": "+1 1234567890", "conference_url": "https://someUrl.com" }`
selectors	Optional	List	`[name: incidentId ,expression: .responseBody \| fromjson.incident.id]`

Output Field	Type	Example
response	object	`{ "incident": { "id": "PT4KHLK", "type": "incident", "title": "The server is on fire.", .... .... }`
success	Boolean	`success: true \| false`
errorMessage	String	`{ "error": { "message": "Invalid Input Provided", "code": 2001, "errors": [ "Cannot specify both assignments and an escalation policy at the same time" ] } }`

Output Field

Type

Example

response

object

{
"incident": {
    "id": "PT4KHLK",
    "type": "incident",
    "title": "The server is on fire.",
    ....
    ....
}

success

Boolean

success: true | false

errorMessage

String

{
  "error": {
      "message": "Invalid Input Provided",
      "code": 2001,
      "errors": [
          "Cannot specify both assignments and an escalation policy at the same time"
      ]
  }
}

Workflow example
name: create-pagerduty-incident description: '' steps: - name: create type: action action: pagerduty.incident.create version: 1 inputs: token: ${{ :secrets:pagerdutyApiToken }} type: incident title: Test incident service: id: P123456 type: service_reference urgency: low body: type: incident_body details: Test Body incidentKey: a12345-b678910-c111213 escalationPolicy: id: P54321 type: escalation_policy_reference selectors: - name: incidentId expression: .responseBody \| fromjson.incident.id next: end

Workflow example

name: create-pagerduty-incident
description: ''
steps:
  - name: create
    type: action
    action: pagerduty.incident.create
    version: 1
    inputs:
      token: ${{ :secrets:pagerdutyApiToken }}
      type: incident
      title: Test incident 
      service:
        id: P123456
        type: service_reference
      urgency: low
      body:
        type: incident_body
        details: Test Body
      incidentKey: a12345-b678910-c111213
      escalationPolicy:
        id: P54321
        type: escalation_policy_reference
      selectors:
        - name: incidentId
          expression: .responseBody | fromjson.incident.id
    next: end

Updates an existing PagerDuty incident's properties such as status, priority, title, assignments, and other attributes.

Input Field	Optionality	Type	Example
token	Required	String	`${{ :secrets:pagerdutyApiToken }}`
incidentId	Required	String	`1234567`
from	Optional	String	`abc@example.com` The from field is required for account tokens but optional for user tokens
type	Required	String	`"incident"`
status	Optional	String	`“acknowledged“`
priority	Optional	Map	`"priority": { "id": "P53ZZH5", "type": "priority_reference" }`
title	Optional	String	`“Test Incident 2“`
escalation_level	Optional	Integer	`1`
assignments	Optional	List	`[ { "assignee": { "id": "P11223", "type": "user_reference" } } ]`
incident_type	Optional	Map	`"incident_type": { "name": "major_incident" }`
escalation_policy	Optional	Map	`"escalation_policy": { "id": "PT20YPA", "type": "escalation_policy_reference" }`
urgency	Optional	String	`“low” or “high”`
conference_bridge	Optional	Map	`"conference_bridge": { "conference_number": "+1 1234567890", "conference_url": "https://someUrl.com" }`
service	Optional	Map	`"service": { "id": "PV5L94Z", "type": "service_reference" }`
resolution	Optional	String	`“resolved“`
selectors	Optional	List	`[name: incidentId ,expression: .responseBody \| fromjson.incident.id]`

Output Field	Type	Example
response	Object	`{ "incident": { "id": "PT4KHLK", "type": "incident", "title": "The server is on fire.", .... .... }`
success	Boolean	`success: true \| false`
errorMessage	String

Workflow example
`name: update-pagerduty-incident description: '' steps: - name: pagerduty_incident_update_1 type: action action: pagerduty.incident.update version: 1 inputs: token: ${{ :secrets:pagerdutyApiToken }} type: incident incidentId: Q1234567890123 status: acknowledged title: Incident Title Updated urgency: low service: id: P123456 type: service_reference conferenceBridge: conference_number: '+1 1234567890' conference_url: test@example.com next: end`

Workflow example

name: update-pagerduty-incident
description: ''
steps:
  - name: pagerduty_incident_update_1
    type: action
    action: pagerduty.incident.update
    version: 1
    inputs:
      token: ${{ :secrets:pagerdutyApiToken }}
      type: incident
      incidentId: Q1234567890123
      status: acknowledged
      title: Incident Title Updated
      urgency: low
      service:
        id: P123456
        type: service_reference
      conferenceBridge:
        conference_number: '+1 1234567890'
        conference_url: test@example.com
    next: end

Prerequisites

Incident actions

Resolve a PagerDuty incident

List PagerDuty incidents

Importante

Get a PagerDuty incident

Create a new PagerDuty incident

Update a PagerDuty incident

PagerDuty actions

Prerequisites.css-21sua1{background:none;border:none;width:0;padding:0;}

Incident actions

List PagerDuty incidents

Get a PagerDuty incident

Create a new PagerDuty incident

Update a PagerDuty incident

Prerequisites