Workflow Integrations

Some Incident Workflow actions leverage a new type of integration, called Workflow Integrations. Workflow Integrations support authentication using API keys and/or OAuth, and provide a lightweight way to connect PagerDuty Incident Workflows with other tools outside of the PagerDuty Operations Cloud.

Workflow Integrations with the following tools are supported:

🚧

Required User Permissions

User with the following roles can add/update/delete Workflow Integration connections:

  • Manager
  • Admin
  • Account Owner

Create a Workflow Integration

Workflow Integrations securely store connection credentials.

  1. In the web app, navigate to Integrations Workflow Integrations.
  2. Click Add Connection to the right of your preferred tool.
Add connection

Add connection

  1. Expand the section below that corresponds to your preferred technology, and enter the requested information:

    1. AWS
      Field NameDescription
      Connection NameThe name for the created connection
      Access Key IDThe associated access key ID
      Secret Access KeyThe associated secret access key
      Role (optional)Role to assume when using this connection. Can be a role ID or full ARN.
      Default RegionThe default region to use when using this connection, e.g., us-east-1
    2. Azure Functions
      Field NameDescription
      Connection NameThe name to give the new connection
      API KeyThe API Key for your Azure Function
      URLThe URL for the connection, e.g., https://<APP_NAME>.azurewebsites.net/api/<FUNCTION_NAME>
    3. Datadog
      Field NameDescription
      Connection NameThe name for the created connection
      API KeyYour Datadog API key. Can be found in Datadog at Organization Settings Access API Keys
      Application KeyYour Datadog application key. Can be found in Datadog at Personal Settings Security Application Keys, or Organization Settings Access Application Keys
    4. Web API
      Field NameDescription
      Connection NameEnter a name for the new connection
      Authentication HeadersEnter the headers to include in Web API calls made with this connection, one per line, e.g., Authorization: Bearer XXXX
      Allowed HostnamesEnter the hostnames to allow sending these credentials to, one per line. An asterisk (*) may be used for subdomains, e.g., example.com, subdomain.example.com or *.example.com
      Health Check URLEnter a URL to monitor the health of this connection
      Health Check MethodSelect which HTTP method to use for the health check request, HEAD or GET
  2. In the field Who can edit or select the connection, select All admins and global managers (default) or All admins, global managers team managers on specific teams. If you choose All admins, global managers team managers on specific teams, select one or more Teams from the Select teams dropdown.

Select team

Select teams

πŸ“˜

Permission Scope

This setting affects who can edit the connection or select the connection when configuring actions in an Incident Workflow. This setting does not affect who can invoke an Incident Workflow; that setting is administered while creating or editing an Incident Workflow.

  1. Click Add.

Delete a Workflow Integration

  1. In the web app, navigate to Integrations Workflow Integrations.
  2. To the right of your preferred connection, click Delete.
  3. In the confirmation modal, click Delete.

Use a Workflow Integration in Incident Workflows

Creating a Workflow Integration will allow you to use some tool-specific Incident Workflow Actions. Please read Incident Workflows for more information.