PagerDuty Connector

Documentation Index

Fetch the complete documentation index at: https://koreai.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Back to Search AI connectors list PagerDuty is an incident management and real-time operational monitoring platform. It detects, routes, and resolves incidents by notifying the right teams when issues occur. The Search AI PagerDuty Connector ingests Schedules and Escalation Policies, making them searchable within Search AI.

​

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

1. Sign in to your PagerDuty account.
2. From the top menu, select Integrations > App Registration to open the My Apps page.
3. Click New App and configure the following fields:

4. Click Register App. Save the generated client credentials for use during connector configuration.

​

Generate an API Token

1. Sign in to your PagerDuty account.
2. From the top menu, select Integrations > API Access Keys.
3. Click Create New API Key and provide a description.
4. 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.

​

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)

Schedules describe on-call rotation schedules for team members. Each ingested schedule record contains the description, schedule layers, users, teams, escalation policy, and total escalation levels.

​

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. The sys_racl field for both content types contains:

• The account name or subdomain.
• Team IDs of all teams associated with the policy or schedule.

Use the Permission Entity APIs to associate individual users with these permission entities.