PagerDuty Automation via Rube MCP
Automate PagerDuty incident management and operations through Composio's PagerDuty toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active PagerDuty connection via
RUBE_MANAGE_CONNECTIONS with toolkit pagerduty
- Always call
RUBE_SEARCH_TOOLS first to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit pagerduty
- If connection is not ACTIVE, follow the returned auth link to complete PagerDuty authentication
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Manage Incidents
When to use: User wants to create, update, acknowledge, or resolve incidents
Tool sequence:
PAGERDUTY_FETCH_INCIDENT_LIST - List incidents with filters [Required]
PAGERDUTY_RETRIEVE_INCIDENT_BY_INCIDENT_ID - Get specific incident details [Optional]
PAGERDUTY_CREATE_INCIDENT_RECORD - Create a new incident [Optional]
PAGERDUTY_UPDATE_INCIDENT_BY_ID - Update incident status or assignment [Optional]
PAGERDUTY_POST_INCIDENT_NOTE_USING_ID - Add a note to an incident [Optional]
PAGERDUTY_SNOOZE_INCIDENT_BY_DURATION - Snooze an incident for a period [Optional]
Key parameters:
statuses[]: Filter by status ('triggered', 'acknowledged', 'resolved')
service_ids[]: Filter by service IDs
urgencies[]: Filter by urgency ('high', 'low')
title: Incident title (for creation)
service: Service object with id and type (for creation)
status: New status for update operations
Pitfalls:
- Incident creation requires a
service object with both id and type: 'service_reference'
- Status transitions follow: triggered -> acknowledged -> resolved
- Cannot transition from resolved back to triggered directly
PAGERDUTY_UPDATE_INCIDENT_BY_ID requires the incident ID as a path parameter
- Snooze duration is in seconds; the incident re-triggers after the snooze period
2. Inspect Incident Alerts and Analytics
When to use: User wants to review alerts within an incident or analyze incident metrics
Tool sequence:
PAGERDUTY_GET_ALERTS_BY_INCIDENT_ID - List alerts for an incident [Required]
PAGERDUTY_GET_INCIDENT_ALERT_DETAILS - Get details of a specific alert [Optional]
PAGERDUTY_FETCH_INCIDENT_ANALYTICS_BY_ID - Get incident analytics/metrics [Optional]
Key parameters:
incident_id: The incident ID
alert_id: Specific alert ID within the incident
statuses[]: Filter alerts by status
Pitfalls:
- An incident can have multiple alerts; each alert has its own status
- Alert IDs are scoped to the incident
- Analytics data includes response times, engagement metrics, and resolution times
3. Manage Services
When to use: User wants to create, update, or list services
Tool sequence:
PAGERDUTY_RETRIEVE_LIST_OF_SERVICES - List all services [Required]
PAGERDUTY_RETRIEVE_SERVICE_BY_ID - Get service details [Optional]
PAGERDUTY_CREATE_NEW_SERVICE - Create a new technical service [Optional]
PAGERDUTY_UPDATE_SERVICE_BY_ID - Update service configuration [Optional]
PAGERDUTY_CREATE_INTEGRATION_FOR_SERVICE - Add an integration to a service [Optional]
PAGERDUTY_CREATE_BUSINESS_SERVICE - Create a business service [Optional]
PAGERDUTY_UPDATE_BUSINESS_SERVICE_BY_ID - Update a business service [Optional]
Key parameters:
name: Service name
escalation_policy: Escalation policy object with id and type
alert_creation: Alert creation mode ('create_alerts_and_incidents' or 'create_incidents')
status: Service status ('active', 'warning', 'critical', 'maintenance', 'disabled')
Pitfalls:
- Creating a service requires an existing escalation policy
- Business services are different from technical services; they represent business-level groupings
- Service integrations define how alerts are created (email, API, events)
- Disabling a service stops all incident creation for that service
4. Manage Schedules and On-Call
When to use: User wants to view or manage on-call schedules and rotations
Tool sequence:
PAGERDUTY_GET_SCHEDULES - List all schedules [Required]
PAGERDUTY_RETRIEVE_SCHEDULE_BY_ID - Get specific schedule details [Optional]
PAGERDUTY_CREATE_NEW_SCHEDULE_LAYER - Create a new schedule [Optional]
PAGERDUTY_UPDATE_SCHEDULE_BY_ID - Update an existing schedule [Optional]
PAGERDUTY_RETRIEVE_ONCALL_LIST - View who is currently on-call [Optional]
PAGERDUTY_CREATE_SCHEDULE_OVERRIDES_CONFIGURATION - Create temporary overrides [Optional]
PAGERDUTY_DELETE_SCHEDULE_OVERRIDE_BY_ID - Remove an override [Optional]
PAGERDUTY_RETRIEVE_USERS_BY_SCHEDULE_ID - List users in a schedule [Optional]
PAGERDUTY_PREVIEW_SCHEDULE_OBJECT - Preview schedule changes before saving [Optional]
Key parameters:
schedule_id: Schedule identifier
time_zone: Schedule timezone (e.g., 'America/New_York')
schedule_layers: Array of rotation layer configurations
since/until: Date range for on-call queries (ISO 8601)
override: Override object with user, start, and end times
Pitfalls:
- Schedule layers define rotation order; multiple layers can overlap
- Overrides are temporary and take precedence over the normal schedule
since and until are required for on-call queries to scope the time range
- Time zones must be valid IANA timezone strings
- Preview before saving complex schedule changes to verify correctness
5. Manage Escalation Policies
When to use: User wants to create or modify escalation policies
Tool sequence:
PAGERDUTY_FETCH_ESCALATION_POLICES_LIST - List all escalation policies [Required]
PAGERDUTY_GET_ESCALATION_POLICY_BY_ID - Get policy details [Optional]
PAGERDUTY_CREATE_ESCALATION_POLICY - Create a new policy [Optional]
PAGERDUTY_UPDATE_ESCALATION_POLICY_BY_ID - Update an existing policy [Optional]
PAGERDUTY_AUDIT_ESCALATION_POLICY_RECORDS - View audit trail for a policy [Optional]
Key parameters:
name: Policy name
escalation_rules: Array of escalation rule objects
num_loops: Number of times to loop through rules before stopping (0 = no loop)
escalation_delay_in_minutes: Delay between escalation levels
Pitfalls:
- Each escalation rule requires at least one target (user, schedule, or team)
escalation_delay_in_minutes defines how long before escalating to the next level
- Setting
num_loops to 0 means the policy runs once and stops
- Deleting a policy fails if services still reference it
6. Manage Teams
When to use: User wants to create or manage PagerDuty teams
Tool sequence:
PAGERDUTY_CREATE_NEW_TEAM_WITH_DETAILS - Create a new team [Required]
Key parameters:
name: Team name
description: Team description
Pitfalls:
- Team names must be unique within the account
- Teams are used to scope services, escalation policies, and schedules
Common Patterns
ID Resolution
Service name -> Service ID:
1. Call PAGERDUTY_RETRIEVE_LIST_OF_SERVICES
2. Find service by name in response
3. Extract id field
Schedule name -> Schedule ID:
1. Call PAGERDUTY_GET_SCHEDULES
2. Find schedule by name in response
3. Extract id field
Incident Lifecycle
1. Incident triggered (via API, integration, or manual creation)
2. On-call user notified per escalation policy
3. User acknowledges -> status: 'acknowledged'
4. User resolves -> status: 'resolved'
Pagination
- PagerDuty uses offset-based pagination
- Check response for
more boolean field
- Use
offset and limit parameters
- Continue until
more is false
Known Pitfalls
ID Formats:
- All PagerDuty IDs are alphanumeric strings (e.g., 'P1234AB')
- Service references require
type: 'service_reference'
- User references require
type: 'user_reference'
Status Transitions:
- Incidents: triggered -> acknowledged -> resolved (forward only)
- Services: active, warning, critical, maintenance, disabled
Rate Limits:
- PagerDuty API enforces rate limits per account
- Implement exponential backoff on 429 responses
- Bulk operations should be spaced out
Response Parsing:
- Response data may be nested under
data or data.data
- Parse defensively with fallback patterns
- Pagination uses
offset/limit/more pattern
Quick Reference
| Task |
Tool Slug |
Key Params |
| List incidents |
PAGERDUTY_FETCH_INCIDENT_LIST |
statuses[], service_ids[] |
| Get incident |
PAGERDUTY_RETRIEVE_INCIDENT_BY_INCIDENT_ID |
incident_id |
| Create incident |
PAGERDUTY_CREATE_INCIDENT_RECORD |
title, service |
| Update incident |
PAGERDUTY_UPDATE_INCIDENT_BY_ID |
incident_id, status |
| Add incident note |
PAGERDUTY_POST_INCIDENT_NOTE_USING_ID |
incident_id, content |
| Snooze incident |
PAGERDUTY_SNOOZE_INCIDENT_BY_DURATION |
incident_id, duration |
| Get incident alerts |
PAGERDUTY_GET_ALERTS_BY_INCIDENT_ID |
incident_id |
| Incident analytics |
PAGERDUTY_FETCH_INCIDENT_ANALYTICS_BY_ID |
incident_id |
| List services |
PAGERDUTY_RETRIEVE_LIST_OF_SERVICES |
(none) |
| Get service |
PAGERDUTY_RETRIEVE_SERVICE_BY_ID |
service_id |
| Create service |
PAGERDUTY_CREATE_NEW_SERVICE |
name, escalation_policy |
| Update service |
PAGERDUTY_UPDATE_SERVICE_BY_ID |
service_id |
| List schedules |
PAGERDUTY_GET_SCHEDULES |
(none) |
| Get schedule |
PAGERDUTY_RETRIEVE_SCHEDULE_BY_ID |
schedule_id |
| Get on-call |
PAGERDUTY_RETRIEVE_ONCALL_LIST |
since, until |
| Create schedule override |
PAGERDUTY_CREATE_SCHEDULE_OVERRIDES_CONFIGURATION |
schedule_id |
| List escalation policies |
PAGERDUTY_FETCH_ESCALATION_POLICES_LIST |
(none) |
| Create escalation policy |
PAGERDUTY_CREATE_ESCALATION_POLICY |
name, escalation_rules |
| Create team |
PAGERDUTY_CREATE_NEW_TEAM_WITH_DETAILS |
name, description |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
1---2name: pagerduty-automation3description: "Automate PagerDuty tasks via Rube MCP (Composio): manage incidents, services, schedules, escalation policies, and on-call rotations. Always search tools first for current schemas."4risk: unknown5source: community6date_added: "2026-02-27"7metadata:8 source: https://skillmd.com/skills/nimoqup046-collab/pagerduty-automation9---1011# PagerDuty Automation via Rube MCP1213Automate PagerDuty incident management and operations through Composio's PagerDuty toolkit via Rube MCP.1415## Prerequisites1617- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)18- Active PagerDuty connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pagerduty`19- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas2021## Setup2223**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.2425261. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds272. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pagerduty`283. If connection is not ACTIVE, follow the returned auth link to complete PagerDuty authentication294. Confirm connection status shows ACTIVE before running any workflows3031## Core Workflows3233### 1. Manage Incidents3435**When to use**: User wants to create, update, acknowledge, or resolve incidents3637**Tool sequence**:381. `PAGERDUTY_FETCH_INCIDENT_LIST` - List incidents with filters [Required]392. `PAGERDUTY_RETRIEVE_INCIDENT_BY_INCIDENT_ID` - Get specific incident details [Optional]403. `PAGERDUTY_CREATE_INCIDENT_RECORD` - Create a new incident [Optional]414. `PAGERDUTY_UPDATE_INCIDENT_BY_ID` - Update incident status or assignment [Optional]425. `PAGERDUTY_POST_INCIDENT_NOTE_USING_ID` - Add a note to an incident [Optional]436. `PAGERDUTY_SNOOZE_INCIDENT_BY_DURATION` - Snooze an incident for a period [Optional]4445**Key parameters**:46- `statuses[]`: Filter by status ('triggered', 'acknowledged', 'resolved')47- `service_ids[]`: Filter by service IDs48- `urgencies[]`: Filter by urgency ('high', 'low')49- `title`: Incident title (for creation)50- `service`: Service object with `id` and `type` (for creation)51- `status`: New status for update operations5253**Pitfalls**:54- Incident creation requires a `service` object with both `id` and `type: 'service_reference'`55- Status transitions follow: triggered -> acknowledged -> resolved56- Cannot transition from resolved back to triggered directly57- `PAGERDUTY_UPDATE_INCIDENT_BY_ID` requires the incident ID as a path parameter58- Snooze duration is in seconds; the incident re-triggers after the snooze period5960### 2. Inspect Incident Alerts and Analytics6162**When to use**: User wants to review alerts within an incident or analyze incident metrics6364**Tool sequence**:651. `PAGERDUTY_GET_ALERTS_BY_INCIDENT_ID` - List alerts for an incident [Required]662. `PAGERDUTY_GET_INCIDENT_ALERT_DETAILS` - Get details of a specific alert [Optional]673. `PAGERDUTY_FETCH_INCIDENT_ANALYTICS_BY_ID` - Get incident analytics/metrics [Optional]6869**Key parameters**:70- `incident_id`: The incident ID71- `alert_id`: Specific alert ID within the incident72- `statuses[]`: Filter alerts by status7374**Pitfalls**:75- An incident can have multiple alerts; each alert has its own status76- Alert IDs are scoped to the incident77- Analytics data includes response times, engagement metrics, and resolution times7879### 3. Manage Services8081**When to use**: User wants to create, update, or list services8283**Tool sequence**:841. `PAGERDUTY_RETRIEVE_LIST_OF_SERVICES` - List all services [Required]852. `PAGERDUTY_RETRIEVE_SERVICE_BY_ID` - Get service details [Optional]863. `PAGERDUTY_CREATE_NEW_SERVICE` - Create a new technical service [Optional]874. `PAGERDUTY_UPDATE_SERVICE_BY_ID` - Update service configuration [Optional]885. `PAGERDUTY_CREATE_INTEGRATION_FOR_SERVICE` - Add an integration to a service [Optional]896. `PAGERDUTY_CREATE_BUSINESS_SERVICE` - Create a business service [Optional]907. `PAGERDUTY_UPDATE_BUSINESS_SERVICE_BY_ID` - Update a business service [Optional]9192**Key parameters**:93- `name`: Service name94- `escalation_policy`: Escalation policy object with `id` and `type`95- `alert_creation`: Alert creation mode ('create_alerts_and_incidents' or 'create_incidents')96- `status`: Service status ('active', 'warning', 'critical', 'maintenance', 'disabled')9798**Pitfalls**:99- Creating a service requires an existing escalation policy100- Business services are different from technical services; they represent business-level groupings101- Service integrations define how alerts are created (email, API, events)102- Disabling a service stops all incident creation for that service103104### 4. Manage Schedules and On-Call105106**When to use**: User wants to view or manage on-call schedules and rotations107108**Tool sequence**:1091. `PAGERDUTY_GET_SCHEDULES` - List all schedules [Required]1102. `PAGERDUTY_RETRIEVE_SCHEDULE_BY_ID` - Get specific schedule details [Optional]1113. `PAGERDUTY_CREATE_NEW_SCHEDULE_LAYER` - Create a new schedule [Optional]1124. `PAGERDUTY_UPDATE_SCHEDULE_BY_ID` - Update an existing schedule [Optional]1135. `PAGERDUTY_RETRIEVE_ONCALL_LIST` - View who is currently on-call [Optional]1146. `PAGERDUTY_CREATE_SCHEDULE_OVERRIDES_CONFIGURATION` - Create temporary overrides [Optional]1157. `PAGERDUTY_DELETE_SCHEDULE_OVERRIDE_BY_ID` - Remove an override [Optional]1168. `PAGERDUTY_RETRIEVE_USERS_BY_SCHEDULE_ID` - List users in a schedule [Optional]1179. `PAGERDUTY_PREVIEW_SCHEDULE_OBJECT` - Preview schedule changes before saving [Optional]118119**Key parameters**:120- `schedule_id`: Schedule identifier121- `time_zone`: Schedule timezone (e.g., 'America/New_York')122- `schedule_layers`: Array of rotation layer configurations123- `since`/`until`: Date range for on-call queries (ISO 8601)124- `override`: Override object with user, start, and end times125126**Pitfalls**:127- Schedule layers define rotation order; multiple layers can overlap128- Overrides are temporary and take precedence over the normal schedule129- `since` and `until` are required for on-call queries to scope the time range130- Time zones must be valid IANA timezone strings131- Preview before saving complex schedule changes to verify correctness132133### 5. Manage Escalation Policies134135**When to use**: User wants to create or modify escalation policies136137**Tool sequence**:1381. `PAGERDUTY_FETCH_ESCALATION_POLICES_LIST` - List all escalation policies [Required]1392. `PAGERDUTY_GET_ESCALATION_POLICY_BY_ID` - Get policy details [Optional]1403. `PAGERDUTY_CREATE_ESCALATION_POLICY` - Create a new policy [Optional]1414. `PAGERDUTY_UPDATE_ESCALATION_POLICY_BY_ID` - Update an existing policy [Optional]1425. `PAGERDUTY_AUDIT_ESCALATION_POLICY_RECORDS` - View audit trail for a policy [Optional]143144**Key parameters**:145- `name`: Policy name146- `escalation_rules`: Array of escalation rule objects147- `num_loops`: Number of times to loop through rules before stopping (0 = no loop)148- `escalation_delay_in_minutes`: Delay between escalation levels149150**Pitfalls**:151- Each escalation rule requires at least one target (user, schedule, or team)152- `escalation_delay_in_minutes` defines how long before escalating to the next level153- Setting `num_loops` to 0 means the policy runs once and stops154- Deleting a policy fails if services still reference it155156### 6. Manage Teams157158**When to use**: User wants to create or manage PagerDuty teams159160**Tool sequence**:1611. `PAGERDUTY_CREATE_NEW_TEAM_WITH_DETAILS` - Create a new team [Required]162163**Key parameters**:164- `name`: Team name165- `description`: Team description166167**Pitfalls**:168- Team names must be unique within the account169- Teams are used to scope services, escalation policies, and schedules170171## Common Patterns172173### ID Resolution174175**Service name -> Service ID**:176```1771. Call PAGERDUTY_RETRIEVE_LIST_OF_SERVICES1782. Find service by name in response1793. Extract id field180```181182**Schedule name -> Schedule ID**:183```1841. Call PAGERDUTY_GET_SCHEDULES1852. Find schedule by name in response1863. Extract id field187```188189### Incident Lifecycle190191```1921. Incident triggered (via API, integration, or manual creation)1932. On-call user notified per escalation policy1943. User acknowledges -> status: 'acknowledged'1954. User resolves -> status: 'resolved'196```197198### Pagination199200- PagerDuty uses offset-based pagination201- Check response for `more` boolean field202- Use `offset` and `limit` parameters203- Continue until `more` is false204205## Known Pitfalls206207**ID Formats**:208- All PagerDuty IDs are alphanumeric strings (e.g., 'P1234AB')209- Service references require `type: 'service_reference'`210- User references require `type: 'user_reference'`211212**Status Transitions**:213- Incidents: triggered -> acknowledged -> resolved (forward only)214- Services: active, warning, critical, maintenance, disabled215216**Rate Limits**:217- PagerDuty API enforces rate limits per account218- Implement exponential backoff on 429 responses219- Bulk operations should be spaced out220221**Response Parsing**:222- Response data may be nested under `data` or `data.data`223- Parse defensively with fallback patterns224- Pagination uses `offset`/`limit`/`more` pattern225226## Quick Reference227228| Task | Tool Slug | Key Params |229|------|-----------|------------|230| List incidents | PAGERDUTY_FETCH_INCIDENT_LIST | statuses[], service_ids[] |231| Get incident | PAGERDUTY_RETRIEVE_INCIDENT_BY_INCIDENT_ID | incident_id |232| Create incident | PAGERDUTY_CREATE_INCIDENT_RECORD | title, service |233| Update incident | PAGERDUTY_UPDATE_INCIDENT_BY_ID | incident_id, status |234| Add incident note | PAGERDUTY_POST_INCIDENT_NOTE_USING_ID | incident_id, content |235| Snooze incident | PAGERDUTY_SNOOZE_INCIDENT_BY_DURATION | incident_id, duration |236| Get incident alerts | PAGERDUTY_GET_ALERTS_BY_INCIDENT_ID | incident_id |237| Incident analytics | PAGERDUTY_FETCH_INCIDENT_ANALYTICS_BY_ID | incident_id |238| List services | PAGERDUTY_RETRIEVE_LIST_OF_SERVICES | (none) |239| Get service | PAGERDUTY_RETRIEVE_SERVICE_BY_ID | service_id |240| Create service | PAGERDUTY_CREATE_NEW_SERVICE | name, escalation_policy |241| Update service | PAGERDUTY_UPDATE_SERVICE_BY_ID | service_id |242| List schedules | PAGERDUTY_GET_SCHEDULES | (none) |243| Get schedule | PAGERDUTY_RETRIEVE_SCHEDULE_BY_ID | schedule_id |244| Get on-call | PAGERDUTY_RETRIEVE_ONCALL_LIST | since, until |245| Create schedule override | PAGERDUTY_CREATE_SCHEDULE_OVERRIDES_CONFIGURATION | schedule_id |246| List escalation policies | PAGERDUTY_FETCH_ESCALATION_POLICES_LIST | (none) |247| Create escalation policy | PAGERDUTY_CREATE_ESCALATION_POLICY | name, escalation_rules |248| Create team | PAGERDUTY_CREATE_NEW_TEAM_WITH_DETAILS | name, description |249250## When to Use251This skill is applicable to execute the workflow or actions described in the overview.