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

# Connecting PagerDuty to Neo

> Make a PagerDuty REST API key and save it in Neo

You connect PagerDuty once at the MSP level, with one REST API key for your PagerDuty account.

## 1. Make the API key

An Admin or Account Owner makes it. In PagerDuty, open **Integrations > API Access Keys**, click **Create New API Key**, give it a description such as "Neo", and leave **Read-only API Key** unticked: a read-only key cannot raise incidents. Copy the key when PagerDuty shows it.

## 2. Add the key in Neo

**1. Open Integrations**

In the Neo Dashboard, open **Integrations** and find the PagerDuty card, under Chat & Alerting.

**2. Enter the details**

* **REST API Key**: the key from step 1.
* **Service Region**: **United States**, or **Europe** when you sign in at `app.eu.pagerduty.com`.
* **PagerDuty User Email**: the email of a user in your PagerDuty account, such as the account owner or a service user for Neo. PagerDuty needs a user on every change, and records Neo's changes, such as a new incident, as made by this user.

**3. Save**

Click **Save settings**. Neo checks the key against PagerDuty and looks up the user before saving, so a wrong key, the wrong region or an email no user has is rejected straight away.

## 3. Turn PagerDuty on per agent

Open the agent, go to the Integrations section, and pick an access profile for the PagerDuty block, or set each area yourself:

| Area | Access levels you can pick | Notes |
| - | - | - |
| **Incidents, Alerts & Notes** | Disabled, Read Only, Read / Write | Raise, read, note, acknowledge, reassign and resolve incidents. Read / Write for an agent that raises incidents. |
| **On-Call, Schedules & Escalation** | Disabled, Read Only, Read / Write | On-calls, schedules and overrides, escalation policies. |
| **Services, Event Routing & Incident Setup** | Disabled, Read Only, Read / Write | Services, maintenance windows, event orchestrations, incident types and fields. Read Only lets the agent find the service to raise on. |
| **Users, Teams & Tags** | Disabled, Read Only, Read / Write | Users, contact methods, teams and members. |
| **Automation, Workflows & Webhooks** | Disabled, Read Only, Read / Write | Automation Actions, incident workflows, webhook subscriptions. |
| **Status Pages & Updates** | Disabled, Read Only, Read / Write | Status pages and their posts. |
| **Analytics, Audit & Account Security** | Disabled, Read Only, Read / Write | Response metrics, the audit trail, IP allow lists and sessions. |

To raise incidents with no technician approval, pick **IT Admin** or **Full Automation**; **Helpdesk** asks a technician before each incident. The agent also needs its PSA permission to add internal notes on tickets. See [PagerDuty API](https://docs.neoagent.io/agents/tools/communication/pagerduty-api.md) for the profiles and what the agent can read and change.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.