# PagerDuty

Manage PagerDuty: incidents, services, schedules, escalations, on-calls. Exposes **36 actions** covering the full API surface
the agent needs - read and write.

## What it can do

| Method | What it does |
| --- | --- |
| `pagerduty_list_incidents` | List incidents - GET /incidents. |
| `pagerduty_get_incident` | Get one incident - GET /incidents/{id}. |
| `pagerduty_create_incident` | Create an incident - POST /incidents. |
| `pagerduty_update_incident` | Update an incident - PUT /incidents/{id}. |
| `pagerduty_manage_incident` | Manage incident status/reassignment - PUT /incidents/{id}. |
| `pagerduty_add_incident_note` | Add a note to an incident - POST /incidents/{id}/notes. |
| `pagerduty_snooze_incident` | Snooze an incident - POST /incidents/{id}/snooze. |
| `pagerduty_acknowledge_incidents` | Acknowledge multiple incidents - PUT /incidents. |
| `pagerduty_resolve_incidents` | Resolve multiple incidents - PUT /incidents. |
| `pagerduty_list_services` | List services - GET /services. |
| `pagerduty_get_service` | Get one service - GET /services/{id}. |
| `pagerduty_create_service` | Create a service - POST /services. |
| `pagerduty_update_service` | Update a service - PUT /services/{id}. |
| `pagerduty_delete_service` | Delete a service - DELETE /services/{id}. |
| `pagerduty_list_schedules` | List schedules - GET /schedules. |
| `pagerduty_get_schedule` | Get one schedule - GET /schedules/{id}. |
| `pagerduty_create_schedule` | Create a schedule - POST /schedules. |
| `pagerduty_update_schedule` | Update a schedule - PUT /schedules/{id}. |
| `pagerduty_delete_schedule` | Delete a schedule - DELETE /schedules/{id}. |
| `pagerduty_list_schedule_overrides` | List schedule overrides - GET /schedules/{id}/overrides. |
| `pagerduty_list_oncalls` | List on-call users - GET /oncalls. |
| `pagerduty_list_escalation_policies` | List escalation policies - GET /escalation_policies. |
| `pagerduty_get_escalation_policy` | Get one escalation policy - GET /escalation_policies/{id}. |
| `pagerduty_create_escalation_policy` | Create an escalation policy - POST /escalation_policies. |
| `pagerduty_update_escalation_policy` | Update an escalation policy - PUT /escalation_policies/{id}. |
| `pagerduty_delete_escalation_policy` | Delete an escalation policy - DELETE /escalation_policies/{id}. |
| `pagerduty_list_users` | List users - GET /users. |
| `pagerduty_get_user` | Get one user - GET /users/{id}. |
| `pagerduty_create_user` | Create a user - POST /users. |
| `pagerduty_update_user` | Update a user - PUT /users/{id}. |
| `pagerduty_delete_user` | Delete a user - DELETE /users/{id}. |
| `pagerduty_list_teams` | List teams - GET /teams. |
| `pagerduty_get_team` | Get one team - GET /teams/{id}. |
| `pagerduty_list_priorities` | List priorities - GET /priorities. |
| `pagerduty_get_event_orchestration` | Get an event orchestration - GET /event_orchestrations/{id}. |
| `pagerduty_update_event_orchestration` | Update an event orchestration - PUT /event_orchestrations/{id}. |

## How to get credentials

This connector uses an **API key / token**. Create one in the provider
dashboard, then paste it into FlyMyAI:

- **`PAGERDUTY_API_TOKEN`** - PagerDuty - Integrations - API Access Keys - Create New API Key. (https://support.pagerduty.com/docs/api-access-keys)

## Fields to fill in FlyMyAI

| FlyMyAI field | Where it comes from |
| --- | --- |
| `PAGERDUTY_API_TOKEN` | PagerDuty - Integrations - API Access Keys - Create New API Key. |

## Troubleshooting

- **`401 Unauthorized` / `403 Forbidden`** - the token is wrong, expired, or missing a required scope - regenerate it.
- **`429 Too Many Requests`** - you hit the provider rate limit; retry after a short backoff.
- **Unexpected `4xx` on writes** - double-check required fields; the agent confirms before write actions.

## Links

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