PagerDuty

Developer tools

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.

About PagerDuty

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.

Tools

What your agent can do in PagerDuty.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own PagerDuty connection.

  • List incidents

    Read
    pagerduty_list_incidents

    List open and recent incidents.

  • Get an incident

    Read
    pagerduty_get_incident

    Read an incident's details and status.

  • Create an incident

    Write
    pagerduty_create_incident

    Open a new incident on a service.

  • Update an incident

    Write
    pagerduty_update_incident

    Acknowledge, resolve or reassign an incident.

  • Add a note

    Write
    pagerduty_add_note

    Add a note to an incident.

  • List on-calls

    Read
    pagerduty_list_oncalls

    See who is on call for each schedule.

  • List services

    Read
    pagerduty_list_services

    List the services in the account.

Control

Limits you can set.

You decide what your agent may do in PagerDuty, and Agent200 runs every call within those limits.

  • 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

Connect PagerDuty
in three steps.

  1. 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.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 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.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // 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);
    }
  3. 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.

    run.js
    Conceptual example
    Run a request with the connector's tools
    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);

Access

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.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the PagerDuty connector and how to use it.

Agent brief
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/

This page is also available as Markdown, for agents and LLMs: /connectors/pagerduty.md

Guides

Use PagerDuty with the AI you build on.

Step-by-step setup for PagerDuty with a specific model, assistant or agent framework.

FAQ

PagerDuty and Agent200, answered.

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.

  • GitHub

    GitHub

    Read repositories and work with issues and pull requests as the connected user.

    Managed OAuth Developer tools
  • GitLab

    GitLab

    Review merge requests, file issues, read code and check pipelines in your users' GitLab projects.

    Managed OAuth Developer tools
  • Bitbucket

    Bitbucket

    List and open pull requests, comment, read code and check pipelines in your users' Bitbucket workspaces.

    Managed OAuth Developer tools
  • Jira

    Jira

    Search, create and transition Jira issues for the connected user.

    Managed OAuth Developer tools
200 OK

Start with PagerDuty.
Your agent does the rest.

Your users connect their own PagerDuty accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)