Skip to main content
Flow uses this integration to run PagerDuty actions from automations with the team connection selected during setup. Admins choose which actions that team can use, and automation runs call only those allowed actions through the connection.

Prepare in PagerDuty

Create a PagerDuty REST API key with access to the data and actions your team needs. Use a read-only key for read actions. Incident changes need a key with write access.Flow checks the key by reading the PagerDuty user list before it saves the connection. The key must permit this read. General access keys can be read-only. User keys inherit the user’s access. This check does not confirm permission to change incidents.To create a general access key, ask a PagerDuty administrator or account owner to open Integrations > API Access Keys and select Create New API Key. See PagerDuty API access keys for the available key types.Use a REST API key. An Events API routing key does not support these actions.For Create incident, Create incident note, and Update incident, supply From with the email address of a valid user in your PagerDuty account. PagerDuty uses this email to identify who makes the change. See PagerDuty incident requirements.

Connect in Flow

1

Find the PagerDuty integration

  1. Open Integrations.
  2. Choose Add connection.
  3. In Add connection, search for PagerDuty.
  4. Select the PagerDuty card.
Open Flow
2

Connect

  1. Pick the team that will use the connection.
  2. Select the PagerDuty actions that team’s automations need.
  3. Enter your PagerDuty REST API key in the credential form.
  4. Submit the form to save the connection.

Permissions and scopes

This integration does not define provider scopes.

Supported actions