---
title: "PagerDuty integration for LuumenAI"
url: "https://www.luumen.ai/integrations/pagerduty/"
entity: SoftwareIntegration
category: "Incident response"
audience: "SRE, DevOps, platform engineering, IT operations"
---

# PagerDuty integration for LuumenAI

On-call, escalation, and timelines from the session.

## What LuumenAI can do with PagerDuty

LuumenAI connects to PagerDuty with an API token and exposes 356 tools (195 read-only · 104 write · 57 destructive). Reads answer immediately; writes are shown as a plan and require approval by default, configurable per tool by an administrator.

## Key facts

- Authentication: API token
- Tools available: 356 tools (195 read-only · 104 write · 57 destructive)
- Plan: available on all plans
- Category: Incident response

## About PagerDuty with LuumenAI

Keep PagerDuty in step with the fix. LuumenAI sees open incidents and who is on call, escalates with context attached, and keeps the timeline updated as governed actions run — so the record matches what actually happened.

## Example tools

Read-only (195 in total):

- `PAGERDUTY_AGGREGATE_ESCALATION_POLICY_INCIDENT_METRICS` — This endpoint analyzes and aggregates incident metrics across all escalation policies in PagerDuty.
- `PAGERDUTY_AGGREGATE_INCIDENT_METRICS_WITH_FILTERS` — Retrieves and aggregates metrics for incidents across all services in PagerDuty.
- `PAGERDUTY_AUDIT_ESCALATION_POLICY_RECORDS` — Retrieves the audit records for a specific escalation policy in PagerDuty.
- `PAGERDUTY_COUNT_PAUSED_INCIDENT_REPORTS` — Retrieves the count of paused incident reports in the PagerDuty system.
- `PAGERDUTY_FETCH_CACHE_VARIABLE_FOR_EVENT_ORCHESTRATION` — Retrieves detailed information about a specific cache variable in a PagerDuty event orchestration.
- `PAGERDUTY_FETCH_CUSTOM_INCIDENT_FIELD_BY_ID` — Retrieves detailed information about a specific custom field associated with incidents in PagerDuty.
- `PAGERDUTY_FETCH_ESCALATION_POLICES_LIST` — Retrieves a list of escalation policies configured in the PagerDuty account.
- `PAGERDUTY_FETCH_EVENT_ORCHESTRATIONS` — Retrieves a list of event orchestrations configured in the PagerDuty account.

Write and destructive (161 in total, approval required by default):

- `PAGERDUTY_ADD_SERVICE_TO_INCIDENT_WORKFLOW_TRIGGER` — Adds a service to an existing incident workflow trigger in PagerDuty, enabling the trigger to fire for incidents on that service.
- `PAGERDUTY_ASSOCIATE_SERVICE_DEPENDENCIES` — Associates multiple service dependencies in PagerDuty, allowing you to define relationships between supporting and dependent services.
- `PAGERDUTY_ASSOCIATE_TEAM_WITH_AUTOMATION_ACTION` — This endpoint associates a specific team with an automation action in PagerDuty.
- `PAGERDUTY_CONVERT_SERVICE_RULE_BY_ID` — Converts a service's Event Rules to Event Orchestration rules.
- `PAGERDUTY_CREATE_A_CUSTOM_FIELD_FOR_AN_INCIDENT_TYPE` — Create a Custom Field for an Incident Type.
- `PAGERDUTY_CREATE_A_FIELD_OPTION_FOR_A_CUSTOM_FIELD` — Creates a new field option for a custom field on an incident type.
- `PAGERDUTY_CREATE_AN_INCIDENT_TYPE` — Create a new incident type.
- `PAGERDUTY_CREATE_A_TRIGGER` — Creates a new incident workflow trigger in PagerDuty.

## Frequently asked questions

### How does LuumenAI connect to PagerDuty?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

### Can LuumenAI change things in PagerDuty on its own?

Read actions answer immediately. Anything that writes is shown as a plan and requires approval by default, including the 57 actions classified as destructive. Administrators configure that per tool.

### Is there an audit trail?

Every call to PagerDuty — read or write, approved or declined — is recorded with the actor, the input, and the result.

Full page: https://www.luumen.ai/integrations/pagerduty/