> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/automate/connectors/pagerduty.md).

# PagerDuty

Connect PagerDuty to investigate and manage incidents from Agent Mode

Connect PagerDuty to bring incident, service, and on-call context into Agent Mode and take response actions from the same investigation.

This connector is for Agent Mode. To send monitor notifications to PagerDuty, configure a [PagerDuty Destination](/automate/connected-apps/pagerduty.md).

## What You Can Do

**Read and investigate**

> Who is on call for the payments service, what incidents are currently open, and have we seen this failure mode before?
>
> Summarize this incident's alerts, responder notes, affected service, and recent incident history.

**Take action**

> Acknowledge the PagerDuty incident linked to this monitor, add a note with the investigation summary, and tell me who owns the next escalation.
>
> Create an incident for this confirmed checkout outage with the relevant service, urgency, and groundcover investigation link.

The actions Agent Mode can take depend on the connected user's PagerDuty permissions and the enabled tools.

## Setup with an API Token

PagerDuty uses API tokens by default.

1. A workspace admin goes to **Integrations → Connectors → Org Connectors**, selects **PagerDuty**, and enables it.
2. The admin enters a PagerDuty API token to discover the available tools and reviews the [tool restrictions](/automate/connectors/mcp.md#managing-tool-restrictions).
3. Each user goes to **Integrations → Connectors → My Connections**, selects **PagerDuty**, and clicks **Connect**.
4. Enter a personal PagerDuty API token.

## Optional: Switch to OAuth

After registering an OAuth client in PagerDuty, a workspace admin can switch the connector to OAuth:

1. Copy the OAuth client's **Client ID** and **Client Secret**.
2. In groundcover, open **Integrations → Connectors → Org Connectors → PagerDuty**.
3. Under **General Information**, click **Edit** and set **Authentication Method** to **OAuth**.
4. Enter the Client ID and Client Secret, then click **Save**.
5. Click **Connect** under **Tool Restrictions** and complete authorization.

New personal connections use OAuth after the switch; existing token connections continue to work. Switching back to **Token** removes the stored OAuth client, but existing OAuth connections continue until they expire and must then reconnect with a token.

{% hint style="info" %}
Agent Mode acts with the connected user's PagerDuty permissions, subject to groundcover's tool restrictions. Write actions may require approval.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.groundcover.com/automate/connectors/pagerduty.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.