Automate PagerDuty Incident Management

Automates PagerDuty incident management and operations - incidents, services, on-call schedules, escalation policies, and teams - through Composio's PagerDuty toolkit accessed via Rube MCP.

Use this skill when creating, updating, acknowledging, or resolving incidents, reviewing incident alerts and analytics, managing technical or business services, viewing/managing on-call schedules and rotations, or creating/modifying escalation policies. Not a fit for on-call tools other than PagerDuty, or for tasks unrelated to incident/service/schedule management.

Setup requires Rube MCP connected (no API keys needed), an active PagerDuty connection verified via RUBE_MANAGE_CONNECTIONS with toolkit pagerduty, and calling RUBE_SEARCH_TOOLS first for current tool schemas.

Covers six core workflows. Managing incidents uses PAGERDUTY_FETCH_INCIDENT_LIST (filterable by status/service/urgency), plus optional retrieve/create/update/note/snooze tools - incident creation requires a service object with id and type: 'service_reference', and status transitions are forward-only (triggered to acknowledged to resolved, no reverting from resolved). Inspecting alerts and analytics uses PAGERDUTY_GET_ALERTS_BY_INCIDENT_ID and PAGERDUTY_FETCH_INCIDENT_ANALYTICS_BY_ID, noting each incident can have multiple independently-statused alerts.

Managing services covers listing, retrieving, creating (requires an existing escalation policy), updating, and adding integrations, distinguishing technical services from business services (business-level groupings) - disabling a service stops all incident creation for it. Managing schedules and on-call covers listing/creating/updating schedules with rotation layers, viewing current on-call via PAGERDUTY_RETRIEVE_ONCALL_LIST (requiring since/until ISO 8601 range), and creating/deleting temporary schedule overrides that take precedence over the normal rotation - previewing complex changes before saving is recommended.

Managing escalation policies covers listing, creating, and updating policies with escalation rules requiring at least one target (user, schedule, or team), an escalation_delay_in_minutes between levels, and a num_loops setting (0 means run once and stop) - deleting a policy fails if services still reference it. Managing teams covers creating a team with a unique name, used to scope services/policies/schedules.

Common patterns include resolving service or schedule names to IDs by listing and matching by name, the incident lifecycle (trigger to on-call notification per escalation policy to acknowledge to resolve), and offset-based pagination checking a more boolean field. Known pitfalls cover PagerDuty's alphanumeric ID format with typed references (service_reference, user_reference), rate limiting requiring exponential backoff on 429 responses, and defensively parsing responses that may nest data under data or data.data.

Accessed via Rube MCP wrapping Composio's PagerDuty toolkit, covering PagerDuty's incidents, services, schedules, escalation policies, and teams APIs.

On-call and incident response teams automating PagerDuty operations through an MCP-connected agent who need the exact tool sequence, status transition rules, and pagination/rate-limit handling rather than trial-and-error API calls.

PAGERDUTY_UPDATE_INCIDENT_BY_ID: incident_id="P1234AB", status="resolved"