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.
- In the web app, navigate to Integrations Workflow Integrations.
- Click Add Connection to the right of your preferred tool.
![Add connection](https://files.readme.io/f0547d5-add_connection.png)
Add connection
-
Expand the section below that corresponds to your preferred technology, and enter the requested information:
-
AWS
Field Name Description Connection Name The name for the created connection Access Key ID The associated access key ID Secret Access Key The associated secret access key Role (optional) Role to assume when using this connection. Can be a role ID or full ARN. Default Region The default region to use when using this connection, e.g., us-east-1
-
Azure Functions
Field Name Description Connection Name The name to give the new connection API Key The API Key for your Azure Function URL The URL for the connection, e.g., https://<APP_NAME>.azurewebsites.net/api/<FUNCTION_NAME>
-
Datadog
Field Name Description Connection Name The name for the created connection API Key Your Datadog API key. Can be found in Datadog at Organization Settings Access API Keys Application Key Your Datadog application key. Can be found in Datadog at Personal Settings Security Application Keys, or Organization Settings Access Application Keys -
Web API
Field Name Description Connection Name Enter a name for the new connection Authentication Headers Enter the headers to include in Web API calls made with this connection, one per line, e.g., Authorization: Bearer XXXX
Allowed Hostnames Enter 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 URL Enter a URL to monitor the health of this connection Health Check Method Select which HTTP method to use for the health check request, HEAD
orGET
-
-
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](https://files.readme.io/497d27c-select_teams.png)
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.
- Click Add.
Delete a Workflow Integration
- In the web app, navigate to Integrations Workflow Integrations.
- To the right of your preferred connection, click Delete.
- 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.
Updated about 2 months ago