For the complete documentation index, see llms.txt. This page is also available as Markdown.

PagerDuty

PagerDuty is an incident management platform. Trigger, acknowledge, and resolve incidents via the Events API v2, manage incidents via the REST API, and start workflows from incident webhooks.

Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

Connector
Authentication

PagerDuty (Events API / Routing Key)

Events API v2 Routing Key (Integration Key)

PagerDuty (REST API Key)

REST API Key (General Access)

PagerDuty (OAuth)

OAuth sign-in

PagerDuty (App OAuth)

Credentials

PagerDuty (Events API / Routing Key)

Connect to PagerDuty's Events API v2 to trigger, acknowledge, and resolve incidents using a service Integration/Routing Key (found on a service's Integrations tab). For incident management, triggers, and richer actions, use the REST API Key or OAuth connector instead.

Set up in PagerDuty

  1. In PagerDuty, open the service you want to send events to and go to its Integrations tab.

  2. Add an Events API v2 integration and copy the generated Integration/Routing Key.

Set up in StackAI

  1. Open Settings → Connections, add a connection, and select PagerDuty (Events API / Routing Key).

  2. Enter the credentials and connection details in the fields below.

  3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

Connection fields

StackAI field
Required
What to enter

Events API v2 Routing Key (Integration Key)

Yes

The 32-character Integration/Routing Key from a PagerDuty service's Events API v2 integration (Service > Integrations). This is NOT a REST API key — it only enqueues events to one service. Provider instructions.

Provider documentation: Setup reference.

PagerDuty (REST API Key)

Connect to PagerDuty's REST API with a General Access API key to manage incidents (acknowledge, resolve, add notes) and power incident triggers.

Set up in PagerDuty

  1. Sign in to PagerDuty with an account that can manage API access.

  2. Go to Integrations, then API Access Keys, and create a new General Access REST API key.

  3. Copy the API key value (it is shown only once).

Set up in StackAI

  1. Open Settings → Connections, add a connection, and select PagerDuty (REST API Key).

  2. Enter the credentials and connection details in the fields below.

  3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

Connection fields

StackAI field
Required
What to enter

REST API Key (General Access)

Yes

A General Access REST API key from PagerDuty (Integrations > API Access Keys). This is NOT a service Integration/Routing Key — that one is used by the Events API connector. This key manages incidents, services, and webhooks. Provider instructions.

Provider documentation: Setup reference.

PagerDuty (OAuth)

Connect to PagerDuty via Scoped OAuth for least-privilege access to incidents, services, and webhook subscriptions.

Set up in PagerDuty

  1. Use a PagerDuty account with access to the records and operations that your workflow needs.

  2. If your organization restricts application access or user consent, have its administrator approve the connection before you sign in.

Set up in StackAI

  1. Open Settings → Connections, add a connection, and select PagerDuty (OAuth).

  2. Select Connect, sign in to the provider account, and review the requested access. Complete authorization to return to StackAI.

  3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

StackAI obtains the OAuth credentials during sign-in. You do not need to paste an access token or refresh token.

Provider documentation: Setup reference.

PagerDuty (App OAuth)

Connect to PagerDuty's REST API as the application itself via the client-credentials grant. Ideal for server-side automation and webhook handling with no user in the loop.

Set up in PagerDuty

  1. In the PagerDuty Developer console, register an app and enable the OAuth 2.0 client credentials (App OAuth) grant.

  2. Copy the app's Client ID and Client Secret.

Set up in StackAI

  1. Open Settings → Connections, add a connection, and select PagerDuty (App OAuth).

  2. Enter the credentials and connection details in the fields below.

  3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

Connection fields

StackAI field
Required
What to enter

Client ID

Yes

OAuth 2.0 Client ID from your PagerDuty App registration. Provider instructions.

Client Secret

Yes

Enter the client secret issued for the account or service you are connecting.

Account Subdomain

Yes

Your PagerDuty subdomain (mycompany.pagerduty.com -> 'mycompany'). Used to build the required as_account scope.

Region

Optional / as applicable

PagerDuty account region: 'us' or 'eu'.

Provider documentation: Setup reference.

Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

Use an action

  1. Add the required PagerDuty action to the workflow.

  2. Select a connection when the action requests one.

  3. Complete the required fields. Use the reference picker when a value comes from another workflow step.

  4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

Actions

Trigger Incident

Trigger a new incident in PagerDuty.

Inputs

Field
Type
Required
Description

Summary

expression

Yes

A brief text summary of the event, used as the incident title.

Source

expression

Yes

The unique location of the affected system (hostname or fully qualified domain name).

Severity

select (string)

Yes

The perceived severity of the status the event is describing. Available values: Critical, Error, Warning, Info.

Deduplication Key

expression

No

A unique key to deduplicate alerts. Reuse it to update or de-duplicate an existing incident.

Component

expression

No

The part of the affected system that was responsible for the event.

Group

expression

No

A cluster or grouping of sources.

Class

expression

No

The class/type of the event.

Custom Details

object

No

Additional details about the event as a JSON object.

Client

expression

No

The name of the monitoring client that is triggering this event.

Client URL

expression

No

The URL of the monitoring client that is triggering this event.

Outputs

Field
Type
Description

Status

string

The status of the enqueued event.

Message

string

A human-readable message describing the result.

Deduplication Key

string

The deduplication key for the incident.

Acknowledge Incident

Acknowledge an existing incident in PagerDuty.

Inputs

Field
Type
Required
Description

Deduplication Key

expression

Yes

The deduplication key of the incident to acknowledge.

Outputs

Field
Type
Description

Status

string

The status of the enqueued event.

Message

string

A human-readable message describing the result.

Deduplication Key

string

The deduplication key for the incident.

Resolve Incident

Resolve an existing incident in PagerDuty.

Inputs

Field
Type
Required
Description

Deduplication Key

expression

Yes

The deduplication key of the incident to resolve.

Outputs

Field
Type
Description

Status

string

The status of the enqueued event.

Message

string

A human-readable message describing the result.

Deduplication Key

string

The deduplication key for the incident.

Acknowledge Incident (as User)

Acknowledge a PagerDuty incident on behalf of a user via the REST API.

Inputs

Field
Type
Required
Description

Incident ID

expression

Yes

The PagerDuty incident ID to acknowledge.

Acting User Email

expression

Yes

Email of a valid PagerDuty user to acknowledge on behalf of.

Outputs

Field
Type
Description

Incident ID

string

The unique ID of the incident.

Status

string

The current status of the incident.

Title

string

The title of the incident.

Incident URL

string

A link to view the incident in PagerDuty.

Resolve Incident (with Note)

Resolve a PagerDuty incident with an optional resolution note via the REST API.

Inputs

Field
Type
Required
Description

Incident ID

expression

Yes

The PagerDuty incident ID to resolve.

Acting User Email

expression

Yes

Email of a valid PagerDuty user to resolve on behalf of.

Resolution Note

textarea

No

Optional resolution note describing how the incident was resolved.

Outputs

Field
Type
Description

Incident ID

string

The unique ID of the incident.

Status

string

The current status of the incident.

Title

string

The title of the incident.

Incident URL

string

A link to view the incident in PagerDuty.

Add Note to Incident

Add a note to a PagerDuty incident via the REST API.

Inputs

Field
Type
Required
Description

Incident ID

expression

Yes

The PagerDuty incident ID to add a note to.

Acting User Email

expression

Yes

Email of a valid PagerDuty user to author the note as.

Note Content

textarea

Yes

The text content of the note.

Outputs

Field
Type
Description

Note ID

string

The unique ID of the created note.

Content

string

The content of the created note.

Triggers

A trigger starts a workflow when its configured event occurs. Configure the event and filters before enabling the trigger.

On Incident Triggered

Trigger a workflow every time a PagerDuty incident is triggered.

Required permissions: incidents.read, webhook_subscriptions.write.

Configuration

Field
Type
Required
Description

Service

select (string)

Yes

The PagerDuty service whose incidents should trigger the workflow. Options load from the selected connection.

Event inputs

Field
Type
Required
Description

Event Type

string

Yes

The PagerDuty event type (e.g. incident.triggered).

Incident ID

string

Yes

The unique ID of the incident.

Incident Number

number

No

The human-friendly incident number. Default: 0.

Title

string

No

The incident title. Default: .

Status

string

No

The incident status (triggered/acknowledged/resolved). Default: .

Urgency

string

No

The incident urgency (high/low). Default: .

Service ID

string

No

The ID of the service the incident belongs to. Default: .

Service Name

string

No

The name of the service the incident belongs to. Default: .

Incident URL

string

No

A link to the incident in PagerDuty. Default: .

Occurred At

string

No

When the event occurred (ISO-8601). Default: .

Agent

string

No

Who performed the action (user or service). Default: .

Outputs

Field
Type
Description

Event Type

string

The PagerDuty event type (e.g. incident.triggered).

Incident ID

string

The unique ID of the incident.

Incident Number

number

The human-friendly incident number.

Title

string

The incident title.

Status

string

The incident status.

Urgency

string

The incident urgency (high/low).

Service ID

string

The ID of the service the incident belongs to.

Service Name

string

The name of the service the incident belongs to.

Incident URL

string

A link to the incident in PagerDuty.

Occurred At

string

When the event occurred (ISO-8601).

Agent

string

Who performed the action (user or service).

On Incident Acknowledged

Trigger a workflow every time a PagerDuty incident is acknowledged.

Required permissions: incidents.read, webhook_subscriptions.write.

Configuration

Field
Type
Required
Description

Service

select (string)

Yes

The PagerDuty service whose incidents should trigger the workflow. Options load from the selected connection.

Event inputs

Field
Type
Required
Description

Event Type

string

Yes

The PagerDuty event type (e.g. incident.triggered).

Incident ID

string

Yes

The unique ID of the incident.

Incident Number

number

No

The human-friendly incident number. Default: 0.

Title

string

No

The incident title. Default: .

Status

string

No

The incident status (triggered/acknowledged/resolved). Default: .

Urgency

string

No

The incident urgency (high/low). Default: .

Service ID

string

No

The ID of the service the incident belongs to. Default: .

Service Name

string

No

The name of the service the incident belongs to. Default: .

Incident URL

string

No

A link to the incident in PagerDuty. Default: .

Occurred At

string

No

When the event occurred (ISO-8601). Default: .

Agent

string

No

Who performed the action (user or service). Default: .

Outputs

Field
Type
Description

Event Type

string

The PagerDuty event type (e.g. incident.triggered).

Incident ID

string

The unique ID of the incident.

Incident Number

number

The human-friendly incident number.

Title

string

The incident title.

Status

string

The incident status.

Urgency

string

The incident urgency (high/low).

Service ID

string

The ID of the service the incident belongs to.

Service Name

string

The name of the service the incident belongs to.

Incident URL

string

A link to the incident in PagerDuty.

Occurred At

string

When the event occurred (ISO-8601).

Agent

string

Who performed the action (user or service).

On Incident Resolved

Trigger a workflow every time a PagerDuty incident is resolved.

Required permissions: incidents.read, webhook_subscriptions.write.

Configuration

Field
Type
Required
Description

Service

select (string)

Yes

The PagerDuty service whose incidents should trigger the workflow. Options load from the selected connection.

Event inputs

Field
Type
Required
Description

Event Type

string

Yes

The PagerDuty event type (e.g. incident.triggered).

Incident ID

string

Yes

The unique ID of the incident.

Incident Number

number

No

The human-friendly incident number. Default: 0.

Title

string

No

The incident title. Default: .

Status

string

No

The incident status (triggered/acknowledged/resolved). Default: .

Urgency

string

No

The incident urgency (high/low). Default: .

Service ID

string

No

The ID of the service the incident belongs to. Default: .

Service Name

string

No

The name of the service the incident belongs to. Default: .

Incident URL

string

No

A link to the incident in PagerDuty. Default: .

Occurred At

string

No

When the event occurred (ISO-8601). Default: .

Agent

string

No

Who performed the action (user or service). Default: .

Outputs

Field
Type
Description

Event Type

string

The PagerDuty event type (e.g. incident.triggered).

Incident ID

string

The unique ID of the incident.

Incident Number

number

The human-friendly incident number.

Title

string

The incident title.

Status

string

The incident status.

Urgency

string

The incident urgency (high/low).

Service ID

string

The ID of the service the incident belongs to.

Service Name

string

The name of the service the incident belongs to.

Incident URL

string

A link to the incident in PagerDuty.

Occurred At

string

When the event occurred (ISO-8601).

Agent

string

Who performed the action (user or service).

Important behavior

If an operation is denied, check the connection’s granted permissions and the account’s access in the provider. Reauthorize the connection when it needs additional permissions.

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.

Last updated

Was this helpful?