The PagerDuty connector for Gemini Enterprise lets you perform
insert, delete, update, and read operations on PagerDuty datasets.

## Supported actions

When the PagerDuty connector is enabled, the end user can use natural
language commands in Gemini Enterprise to perform the following actions.

| Action | Description |
|---|---|
| Create incident | Create an incident synchronously without a corresponding event from a monitoring service. |
| Update incident | Acknowledge, resolve, escalate, or reassign an incident. |
| Add note to incident | Add a note to an incident's timeline. |
| Create service | Create a new service. |
| Update service | Update an existing service. |
| Create user | Create a new user account in PagerDuty. |
| Update user | Update an existing user's details. |
| Create on-call override | Create an override for a specific user covering a specified time range on a schedule. |
| Search | Search for incidents, services, users, schedules, and escalation policies. |
| List on-call entries | List the on-call entries during a given time range. |
| List log entries | Get the full timeline of an incident. |

> [!NOTE]
> **Note:** Additional read-only actions are also available.

## Required permissions

To enable Gemini Enterprise to perform federated search using the
PagerDuty data store, you need to enable the following scopes:

<br />

| Scope | Purpose |
|---|---|
| read | Grants read access to PagerDuty resources like incidents, services, and users. |
| write | Grants write access to PagerDuty resources, allowing creation and modification of incidents, services, and users. |

<br />

For information on how to configure these scopes, see [Set redirect URL and scopes](https://docs.cloud.google.com/gemini/enterprise/docs/connectors/pagerduty/pagerduty-configuration.md.txt#set-redirect-url-and-scopes).

## Limitations

This section outlines known issues and limitations that can affect your use of
the PagerDuty data store.


- When creating a new app or adding a data store to an existing one, it's recommended to associate only one data store with actions belonging to a single connector type.

<!-- -->

- Enforcing a VPC Service Controls perimeter on existing PagerDuty data stores is not supported. To enforce VPC Service Controls, you must delete and recreate the data stores. For more information on VPC Service Controls and how to use actions after enabling VPC Service Controls, see [Secure your app with VPC Service Controls](https://docs.cloud.google.com/gemini/enterprise/docs/use-vpc-service-controls.md.txt).

<!-- -->

- The PagerDuty data store is supported only in the `global`, `us`, and `eu` locations.

<br />

## What's next

- To create and configure a connector with PagerDuty, see [Set up a PagerDuty data store](https://docs.cloud.google.com/gemini/enterprise/docs/connectors/pagerduty/set-up-data-store.md.txt).