> ## Documentation Index
> Fetch the complete documentation index at: https://veryfront.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# PagerDuty

> Manage incidents, services, and on-call schedules in PagerDuty

## At a glance

* **Availability**: Experimental ([how to enable](/cloud/integrations)).
* **Auth**: OAuth 2.0.
* **Connection**: A user authorizes the connection in the provider's consent screen.
* **Scopes**: `incidents.read`, `incidents.write`, `services.read`, `oncalls.read`, `users.read`.
* **Docs**: [https://developer.pagerduty.com/docs/user-oauth-token-via-code-grant](https://developer.pagerduty.com/docs/user-oauth-token-via-code-grant)

## Credentials

Set these per environment. See [Connect an integration](/cloud/integrations).

With a managed OAuth app, Connect works without these variables; set them to use your own OAuth app instead.

| Variable                  | Required | Description                                                                                                 |
| ------------------------- | -------- | ----------------------------------------------------------------------------------------------------------- |
| `PAGERDUTY_CLIENT_ID`     | Yes      | PagerDuty OAuth Client ID [Docs](https://developer.pagerduty.com/docs/user-oauth-token-via-code-grant).     |
| `PAGERDUTY_CLIENT_SECRET` | Yes      | PagerDuty OAuth Client Secret [Docs](https://developer.pagerduty.com/docs/user-oauth-token-via-code-grant). |

## Setup

1. **Get a PagerDuty account**: Sign up at [https://www.pagerduty.com](https://www.pagerduty.com) - a free trial or developer account is sufficient for testing.
2. **Register an app**: In PagerDuty go to Integrations > App Registration ([https://app.pagerduty.com/developer/applications](https://app.pagerduty.com/developer/applications)), create an app, and add Scoped OAuth functionality. Select the scopes incidents.read, incidents.write, services.read, oncalls.read, and users.read.
3. **Configure the redirect URI**: Set the redirect URI to your app's /api/auth/pagerduty/callback URL, then copy the Client ID and Client Secret into your .env as PAGERDUTY\_CLIENT\_ID and PAGERDUTY\_CLIENT\_SECRET.
4. **Verify access**: Complete the OAuth flow, then run List Services and List Incidents.

* OAuth endpoints live on identity.pagerduty.com; the REST API lives on api.pagerduty.com
* Creating or updating incidents requires a From header containing the email of a valid PagerDuty user - the tools expose it as a required parameter
* Scoped OAuth tokens expire and are renewed with the refresh token

Provider API reference: [https://developer.pagerduty.com/api-reference/](https://developer.pagerduty.com/api-reference/)

## Tools

| Tool            | Access | Description                                                              |
| --------------- | ------ | ------------------------------------------------------------------------ |
| List Incidents  | Read   | List PagerDuty incidents with optional status, service, and time filters |
| Get Incident    | Read   | Get a PagerDuty incident by ID or incident number                        |
| Create Incident | Write  | Manually trigger a new incident on a service                             |
| Manage Incident | Write  | Acknowledge, resolve, reassign, or escalate an incident                  |
| List Services   | Read   | List PagerDuty services                                                  |
| List On-Calls   | Read   | List on-call entries for schedules, escalation policies, and users       |

## Example prompts

* List my PagerDuty incidents that are triggered or acknowledged and summarize them by service.
* Show who is currently on call in PagerDuty.