> ## Documentation Index
> Fetch the complete documentation index at: https://docs.letsflow.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# PagerDuty
> PagerDuty incident and on-call automation through Flow automations.
export const flowWebUrl = "https://app.letsflow.ai";
Flow uses this integration to run PagerDuty actions from automations with the team connection selected during setup. Admins choose which actions that team can use, and automation runs call only those allowed actions through the connection.
### Prepare in PagerDuty
Create a PagerDuty REST API key with access to the data and actions your team needs. Use a read-only key for read actions. Incident changes need a key with write access.
Flow checks the key by reading the PagerDuty user list before it saves the connection. The key must permit this read. General access keys can be read-only. User keys inherit the user's access. This check does not confirm permission to change incidents.
To create a general access key, ask a PagerDuty administrator or account owner to open **Integrations > API Access Keys** and select **Create New API Key**. See [PagerDuty API access keys](https://support.pagerduty.com/main/docs/api-access-keys) for the available key types.
Use a REST API key. An Events API routing key does not support these actions.
For **Create incident**, **Create incident note**, and **Update incident**, supply `From` with the email address of a valid user in your PagerDuty account. PagerDuty uses this email to identify who makes the change. See [PagerDuty incident requirements](https://docs.pagerduty.com/developer/api/reference/rest/incidents/create-incident).
### Connect in Flow
1. Open **Integrations**.
2. Choose **Add connection**.
3. In **Add connection**, search for **PagerDuty**.
4. Select the **PagerDuty** card.
Open Flow
1. Pick the team that will use the connection.
2. Select the PagerDuty actions that team's automations need.
3. Enter your PagerDuty REST API key in the credential form.
4. Submit the form to save the connection.
## Permissions and scopes
This integration does not define provider scopes.
## Supported actions
| Action | Description | Risk |
| - | - | - |
| Create incident | Creates a PagerDuty incident using automation-provided input. Use it when the automation needs to add this provider record or request. | medium |
| Create incident note | Creates a note on a PagerDuty incident using automation-provided input. Use it when the automation needs to add this provider record or request. | low |
| List contact methods | Reads contact methods for a PagerDuty user. Use it to fetch current provider state without modifying data. | low |
| List incident log entries | Reads log entries for a PagerDuty incident. Use it to fetch current provider state without modifying data. | low |
| List on-calls | Reads PagerDuty on-call assignments. Use it to fetch current provider state without modifying data. | low |
| List schedules | Reads PagerDuty schedules. Use it to fetch current provider state without modifying data. | low |
| List services | Reads PagerDuty services. Use it to fetch current provider state without modifying data. | low |
| Update incident | Updates or triggers a PagerDuty incident using automation-provided input. Use it after the automation has selected the target record or command. | medium |
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.