Authenticating Integrations

For each integration in your runbook, configure the related data connection in Settings > Integrations, as described below.

Auth via header parameters#

For data connections that implement authentication with header parameters, such as PagerDuty, the header parameter name (as documented by the external API site) and header parameter value (typically a secret token distributed by the external API site) must be provided when adding the connection to an application.

Example: PagerDuty

PagerDuty auth example

Auth via query parameters#

For data connections that implement authentication with query parameters, such as Zoom, only the query parameter value (typically a secret distributed by the external API site) must be provided when adding the connection to an application.

Example: Zoom

Zoom auth example

Auth via AWS parameters#

For AWS data connections, such as Lambda, the required combination of authentication parameters 'Access Key', 'Secret Key', and 'Role' depends on the authentication setup of your particular AWS service being connected to. The pair of 'Access Key' and 'Secret Key' authenticates you as an IAM user, and the 'Role' can be used to specify the ARN of an IAM role.

Example: Lambda with all three parameters provided (i.e. authentication as an IAM user assuming an IAM role)

Lambda auth example