| name | pagerduty-automation |
| description | Automate PagerDuty tasks via Rube MCP (Composio): manage incidents, services, schedules, escalation policies, and on-call rotations. Always search tools first for current schemas. |
| type | skill |
| created | 2026-02-27T00:00:00.000Z |
| domain | productivity |
| category | automation |
| risk | critical |
| source | community |
| tags | ["skill","productivity","automation","pagerduty"] |
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: