# PagerDuty for AI agents. Managed auth, ready-made tools.

> Read, open, acknowledge and resolve incidents and check who is on call in PagerDuty on behalf of each of your users.

- Page: https://www.agent200.com/connectors/pagerduty/
- Category: Developer tools
- Authentication: Managed OAuth
- Identifier in code: `pagerduty`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-18

## Instructions for AI agents

Connector: PagerDuty, through Agent200. In code: "pagerduty".
What it does: Read, open, acknowledge and resolve incidents and check who is on call in PagerDuty on behalf of each of your users.
Page: https://www.agent200.com/connectors/pagerduty/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on PagerDuty's own page, through the authorization link Agent200 returns. Never ask a user for a PagerDuty password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: pagerduty_list_incidents, pagerduty_get_incident, pagerduty_list_oncalls, pagerduty_list_services. Write tools: pagerduty_create_incident, pagerduty_update_incident, pagerduty_add_note. Name "pagerduty" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/connectors/pagerduty/framework/claude/
   https://www.agent200.com/connectors/pagerduty/framework/chatgpt/
   https://www.agent200.com/connectors/pagerduty/framework/claude-code/
   https://www.agent200.com/connectors/pagerduty/framework/muse/
   https://www.agent200.com/connectors/pagerduty/framework/grok-bot/
   https://www.agent200.com/connectors/pagerduty/framework/openai-dots/
   https://www.agent200.com/connectors/pagerduty/framework/claude-duet/
   https://www.agent200.com/connectors/pagerduty/framework/hermes-agent/
   https://www.agent200.com/connectors/pagerduty/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

## About

With the PagerDuty connector, your agent works in each user's own PagerDuty account. It can list and read incidents, open an incident, acknowledge or resolve one, add a note and check who is on call, using only the tools your project allows.

PagerDuty is an incident management platform that alerts the right people when systems have problems.

## PagerDuty tools

- **List incidents** (`pagerduty_list_incidents`, read): List open and recent incidents.
- **Get an incident** (`pagerduty_get_incident`, read): Read an incident's details and status.
- **Create an incident** (`pagerduty_create_incident`, write): Open a new incident on a service.
- **Update an incident** (`pagerduty_update_incident`, write): Acknowledge, resolve or reassign an incident.
- **Add a note** (`pagerduty_add_note`, write): Add a note to an incident.
- **List on-calls** (`pagerduty_list_oncalls`, read): See who is on call for each schedule.
- **List services** (`pagerduty_list_services`, read): List the services in the account.

## Limits you can set

**Turn single tools on or off.** Let the agent read incidents and on-call schedules, and switch off `pagerduty_create_incident` so it can never page anyone.

**Restrict what the agent reaches.** Choose the endpoints and scopes a project may use, for example incidents but not services. A call outside them is refused.

## Get started

### Step 1: Set up the SDK

Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 2: Let your user connect PagerDuty

Each end user authorizes their own PagerDuty account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

File `connect.js`:

```js
// Each end user authorizes their own PagerDuty account, once.
const connection = await agent200
  .user("user_123")
  .connect("pagerduty");

if (connection.authorizationUrl) {
  // Show this link to your user; Agent200 handles the rest.
  console.log(connection.authorizationUrl);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 3: Run with the PagerDuty tools

Name the user, the model and the tools. The model decides which PagerDuty tools to call, and Agent200 executes them with that user's connection.

File `run.js`:

```js
const result = await agent200
  .user("user_123")
  .run({
    model: "openai/gpt-5.6-sol",
    input: "Who is on call for the payments service right now",
    tools: ["pagerduty"],
  });

console.log(result.output);
```

(Conceptual example of the Agent200 SDK.)

## Sign-in and permissions

**Who signs in.** Each of your users, once, on PagerDuty's own sign-in page. You never see or store their PagerDuty password.

**What access is requested.** The scopes the connection needs, such as reading incidents, writing incidents or reading on-call schedules, listed on PagerDuty's authorization screen. Users can remove the app later from their PagerDuty account settings.

## Example requests

- "Who is on call for the payments service right now"
- "List the open high urgency incidents"
- "Acknowledge the incident about the checkout API"
- "Add a note that the fix is deployed"

## Guides: PagerDuty with your AI framework

- [PagerDuty + Claude](https://www.agent200.com/connectors/pagerduty/framework/claude.md): Set up PagerDuty for Claude with Agent200, then check which tools are available to your agent.
- [PagerDuty + ChatGPT](https://www.agent200.com/connectors/pagerduty/framework/chatgpt.md): Set up PagerDuty for ChatGPT with Agent200, then check which tools are available to your agent.
- [PagerDuty + Claude Code](https://www.agent200.com/connectors/pagerduty/framework/claude-code.md): Set up PagerDuty for Claude Code with Agent200, then check which tools are available to your agent.
- [PagerDuty + Muse](https://www.agent200.com/connectors/pagerduty/framework/muse.md): Set up PagerDuty for Muse with Agent200, then check which tools are available to your agent.
- [PagerDuty + Grok Bot](https://www.agent200.com/connectors/pagerduty/framework/grok-bot.md): Set up PagerDuty for Grok Bot with Agent200, then check which tools are available to your agent.
- [PagerDuty + OpenAI Dots](https://www.agent200.com/connectors/pagerduty/framework/openai-dots.md): Set up PagerDuty for OpenAI Dots with Agent200, then check which tools are available to your agent.
- [PagerDuty + Claude Duet](https://www.agent200.com/connectors/pagerduty/framework/claude-duet.md): Set up PagerDuty for Claude Duet with Agent200, then check which tools are available to your agent.
- [PagerDuty + Hermes Agent](https://www.agent200.com/connectors/pagerduty/framework/hermes-agent.md): Set up PagerDuty for Hermes Agent with Agent200, then check which tools are available to your agent.
- [PagerDuty + OpenClaw](https://www.agent200.com/connectors/pagerduty/framework/openclaw.md): Set up PagerDuty for OpenClaw with Agent200, then check which tools are available to your agent.

## FAQ

### Who handles the PagerDuty OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for PagerDuty.

### Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's PagerDuty connection, never another user's. It cannot reach anything the user or PagerDuty has not authorized.

### Can I limit what my agent can do in PagerDuty?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

## Related connectors

- [GitHub](https://www.agent200.com/connectors/github.md): Read repositories and work with issues and pull requests as the connected user.
- [GitLab](https://www.agent200.com/connectors/gitlab.md): Review merge requests, file issues, read code and check pipelines in your users' GitLab projects.
- [Bitbucket](https://www.agent200.com/connectors/bitbucket.md): List and open pull requests, comment, read code and check pipelines in your users' Bitbucket workspaces.
- [Jira](https://www.agent200.com/connectors/jira.md): Search, create and transition Jira issues for the connected user.

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
