| Specification | Details |
|---|---|
| Repository type | Cloud |
| Supported content | Schedules, Escalation Policies |
| RACL support | Yes |
| Content filtering | No |
Prerequisites
- A PagerDuty account with access to all policies and schedules to be ingested.
Authentication Options
Search AI supports two authentication methods for PagerDuty:- OAuth 2.0 — Register Search AI as an OAuth app in PagerDuty and use client credentials.
- API Token — Generate an API token directly from PagerDuty.
Set Up OAuth Authentication
- Sign in to your PagerDuty account.
- From the top menu, select Integrations > App Registration to open the My Apps page.
- Click New App and configure the following fields:
| Field | Value |
|---|---|
| Name | Unique name for the application |
| Description | Brief description of the app |
| Functionality | OAuth 2.0 |
| Redirect URL | JP Region: https://jp-bots-idp.kore.ai/workflows/callback DE Region: https://de-bots-idp.kore.ai/workflows/callback Prod: https://idp.kore.com/workflows/callback |
| Permission Scope | Read Access for: Escalation Policies, Schedules, Users, Tags, Teams |
- Click Register App. Save the generated client credentials for use during connector configuration.
Generate an API Token
- Sign in to your PagerDuty account.
- From the top menu, select Integrations > API Access Keys.
- Click Create New API Key and provide a description.
- Click Create Key and save the generated key.
Configure the Connector in Search AI
On the Authorization tab of the PagerDuty Connector, enter the following details and click Connect.| Field | Description |
|---|---|
| Name | Unique name for the connector |
| Authorization Type | API Key: Enter the API key generated in PagerDuty. OAuth 2.0: Set grant type to Authorization Code and provide the client credentials. |
Content Ingestion
On the Configuration tab, click Sync Now to immediately ingest content, or use the scheduler to run sync at regular intervals. Escalation Policies define how incidents are escalated within a team. Each ingested policy record contains:- Policy name (title field)
- Description, escalation rules, teams, handoff notifications, and total levels (content field)
RACL Support
PagerDuty organizes access around accounts and teams. Users with Account Owner, Admin, or Billing Contact roles have access to all account-wide data. All members of a team have access to that team’s escalation policies and schedules. Thesys_racl field for both content types contains:
- The account name or subdomain.
- Team IDs of all teams associated with the policy or schedule.