Pagerduty Provider allows integration with PagerDuty to create, manage, and synchronize incidents and alerts within Keep.
The Pagerduty Provider enables integration with PagerDuty to create, manage, and synchronize incidents and alerts within Keep. It supports both direct API key authentication and OAuth2, allowing greater flexibility for secure integration.
This provider requires authentication.
Certain scopes may be required to perform specific actions or queries via the provider. Below is a summary of relevant scopes and their use cases:
This provider can be used in workflows.
As “step” to query data, example:
As “action” to make changes or update data, example:
Check the following workflow example:
This provider pulls topology to Keep. It could be used in correlations and mapping, and as a context for alerts and incidents.
To connect Keep to PagerDuty:
You can find your routing key in the PagerDuty (integration key in PagerDuty UI) web app under Services > Service Directory > Your service > Integrations > Expand Events API, and select the integration you want to use. You can find your API key in the PagerDuty web app under Configuration > API Access.
The routing_key is used to post events to PagerDuty using the events API. The api_key is used to create incidents using the incidents API.
If you would like to use OAuth in the open-source, where you self-host Keep, you can do so by following these step:
PAGERDUTY_CLIENT_ID
and PAGERDUTY_CLIENT_SECRET
environment variables in your Keep backend deployment.
By default, when Keep installs itself as a webhook integration, it subscribes to all incident events (“Account Scope”).
If you wish to limit Keep to some specific services, you can do so by selecting the Service scope and selecting the services you want to subscribe to.
Find this page under Integrations > Generic Webhooks (v3)
The provider uses either the events API or the incidents API to create an alert or an incident. The choice of API to use is determined by the presence of either a routing_key or an api_key.
An expired trial while using the free version of PagerDuty may result in the “pagerduty scopes are invalid” error at Keep.
The webhook integration adds Keep as a destination within the “Integrations” API within Pagerduty. This grants Keep access to the following scopes within Pagerduty:
webhook_subscriptions_read
webhook_subscriptions_write
Pagerduty Provider allows integration with PagerDuty to create, manage, and synchronize incidents and alerts within Keep.
The Pagerduty Provider enables integration with PagerDuty to create, manage, and synchronize incidents and alerts within Keep. It supports both direct API key authentication and OAuth2, allowing greater flexibility for secure integration.
This provider requires authentication.
Certain scopes may be required to perform specific actions or queries via the provider. Below is a summary of relevant scopes and their use cases:
This provider can be used in workflows.
As “step” to query data, example:
As “action” to make changes or update data, example:
Check the following workflow example:
This provider pulls topology to Keep. It could be used in correlations and mapping, and as a context for alerts and incidents.
To connect Keep to PagerDuty:
You can find your routing key in the PagerDuty (integration key in PagerDuty UI) web app under Services > Service Directory > Your service > Integrations > Expand Events API, and select the integration you want to use. You can find your API key in the PagerDuty web app under Configuration > API Access.
The routing_key is used to post events to PagerDuty using the events API. The api_key is used to create incidents using the incidents API.
If you would like to use OAuth in the open-source, where you self-host Keep, you can do so by following these step:
PAGERDUTY_CLIENT_ID
and PAGERDUTY_CLIENT_SECRET
environment variables in your Keep backend deployment.
By default, when Keep installs itself as a webhook integration, it subscribes to all incident events (“Account Scope”).
If you wish to limit Keep to some specific services, you can do so by selecting the Service scope and selecting the services you want to subscribe to.
Find this page under Integrations > Generic Webhooks (v3)
The provider uses either the events API or the incidents API to create an alert or an incident. The choice of API to use is determined by the presence of either a routing_key or an api_key.
An expired trial while using the free version of PagerDuty may result in the “pagerduty scopes are invalid” error at Keep.
The webhook integration adds Keep as a destination within the “Integrations” API within Pagerduty. This grants Keep access to the following scopes within Pagerduty:
webhook_subscriptions_read
webhook_subscriptions_write