--- title: PagerDuty Incident actions source: https://docs.newrelic.com/docs/workflow-automation/setup-and-configure/actions-catalog/pagerduty/pagerduty-incident --- This page provides a comprehensive reference for pagerduty incident actions available in the workflow automation actions catalog. These actions enable you to pagerduty incident management. ## 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 **Resolve a PagerDuty incident** Resolves a PagerDuty incident by updating its status to resolved with optional resolution notes. ### Inputs | 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]` | ### Outputs | Output Field | Type | Example | | ---------------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **response** | object | ```yaml { "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 ` | ### Example | Workflow example | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ```yaml 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 ``` | **List PagerDuty incidents** Retrieves a list of incidents from PagerDuty with optional filtering parameters such as date ranges and status. ### Inputs | Input Field | Optionality | Type | Example | | -------------- | ----------- | ------ | ---------------------------------------------------------------------- | | **token** | Required | String | `${{ :secrets:pagerdutyApiToken }}` | | **parameters** | Optional | Map | ```yaml { offset: 0 , incident_key: 1234-5678-0101123 } ``` | | **selectors** | Optional | List | `[name: incidentId ,expression: .responseBody | fromjson.incident.id]` | > #### ⚠️ IMPORTANT > > The [PagerDuty List API](https://developer.pagerduty.com/api-reference/9d0b4b12e36f9-list-incidents) supports multiple optional query parameters, which can be efficiently handled using a parameter map ### Outputs | Output Field | Type | Example | | ---------------- | ------- | ----------------------------------------------------------------------------------------------------------------- | | **response** | object | ```yaml { “incidents”: [ { “incident_number”: 1234, “title”: “Test Incident 1" ... } ] } ``` | | **success** | Boolean | `success: true | false` | | **errorMessage** | String | ```yaml "error": { "message": "The request took too long to process.", "code": 2016 } ``` | ### Example | Workflow example | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ```yaml 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 ``` | **Get a PagerDuty incident** Get a PagerDuty incident. ### Inputs | Input Field | Optionality | Type | Example | | -------------- | ----------- | ------ | ---------------------------------------------------------------------- | | **token** | Required | String | `${{ :secrets:pagerdutyApiToken }}` | | **incidentId** | Required | String | `Q123456789` | | **parameters** | Optional | Map | ```yaml { include[] : “services“ } ``` | | **selectors** | Optional | List | `[name: incidentId ,expression: .responseBody | fromjson.incident.id]` | ### Outputs | Output Field | Type | Example | | ---------------- | ------- | ----------------------------------------------------------------------------------------------------------------- | | **response** | Object | ```yaml { “incidents”: [ { “incident_number”: 1234, “title”: “Test Incident 1" ... } ] } ``` | | **success** | Boolean | `success: true | false` | | **errorMessage** | String | ```yaml "error": { "message": "The request took too long to process.", "code": 2016 } ``` | ### Example | Workflow example | | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ```yaml 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 ``` | **Create a new PagerDuty incident** Creates a new incident in PagerDuty with specified service, title, priority, and other optional attributes. ### Inputs | Input Field | Optionality | Type | Example | | -------------------- | ----------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **token** | Required | String | `${{ :secrets:pagerdutyApiToken }}` | | **type** | Required | String | `"Incident"` | | **title** | Required | String | `"Test Incident"` | | **service** | Required | Map | ```yaml "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 | ```yaml "priority": { "id": "P53ZZH5", "type": "priority_reference" } ``` | | **urgency** | Optional | String | `"Low"` | | **body** | Optional | Map | ```yaml "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 | ```yaml [ { "assignee": { "id": "P11223", "type": "user_reference" } } ] ``` | | **incidentType** | Optional | String | ```yaml "incident_type": { "name": "major_incident" } ``` | | **escalationPolicy** | Optional | Map | ```yaml "escalation_policy": { "id": "PT20YPA", "type": "escalation_policy_reference" } ``` | | **conferenceBridge** | Optional | Map | ```yaml "conference_bridge": { "conference_number": "+1 1234567890", "conference_url": "https://someUrl.com" } ``` | | **selectors** | Optional | List | `[name: incidentId ,expression: .responseBody | fromjson.incident.id]` | ### Outputs | Output Field | Type | Example | | ---------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **response** | object | ```yaml { "incident": { "id": "PT4KHLK", "type": "incident", "title": "The server is on fire.", .... .... } ``` | | **success** | Boolean | `success: true | false` | | **errorMessage** | String | ```yaml { "error": { "message": "Invalid Input Provided", "code": 2001, "errors": [ "Cannot specify both assignments and an escalation policy at the same time" ] } } ``` | ### Example | Workflow example | | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ```yaml 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 ``` | **Update a PagerDuty incident** Updates an existing PagerDuty incident's properties such as status, priority, title, assignments, and other attributes. ### Inputs | 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 | ```yaml "priority": { "id": "P53ZZH5", "type": "priority_reference" } ``` | | **title** | Optional | String | `"Test Incident 2"` | | **escalation_level** | Optional | Integer | `1` | | **assignments** | Optional | List | ```yaml [ { "assignee": { "id": "P11223", "type": "user_reference" } } ] ``` | | **incident_type** | Optional | Map | ```yaml "incident_type": { "name": "major_incident" } ``` | | **escalation_policy** | Optional | Map | ```yaml "escalation_policy": { "id": "PT20YPA", "type": "escalation_policy_reference" } ``` | | **urgency** | Optional | String | `"low" or "high"` | | **conference_bridge** | Optional | Map | ```yaml "conference_bridge": { "conference_number": "+1 1234567890", "conference_url": "https://someUrl.com" } ``` | | **service** | Optional | Map | ```yaml "service": { "id": "PV5L94Z", "type": "service_reference" } ``` | | **resolution** | Optional | String | `"resolved"` | | **selectors** | Optional | List | `[name: incidentId ,expression: .responseBody | fromjson.incident.id]` | ### Outputs | Output Field | Type | Example | | ---------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------- | | **response** | Object | ```yaml { "incident": { "id": "PT4KHLK", "type": "incident", "title": "The server is on fire.", .... .... } ``` | | **success** | Boolean | `success: true | false` | | **errorMessage** | String | | ### Example | Workflow example | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | ```yaml 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 ``` |