Connect Pagerduty to Slack
Automate Pagerduty and Slack with AI
PagerDuty pages the people who can fix production while everyone else tracks status in Slack. OpenClaw on Operator.io ties PagerDuty and Slack so new incidents open a channel thread with service, severity, and assignee updates as they change, acknowledged and resolved pages post back so the room stops asking the same question, and chat lists open incidents with their Slack thread links. Tell it what is still firing on call and it reads PagerDuty and summarizes in Slack.
It reaches both apps directly or through connectors like Composio MCP and Pipedream MCP, which handle the sign in and token refresh, so there is no Zap to build and no API keys to paste.
What your agent can do with Pagerduty and Slack
What your agent does in 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. Associates a specific service with an incident workflow trigger to automate incident management for that se...
Aggregate escalation policy incident metrics
This endpoint analyzes and aggregates incident metrics across all escalation policies in PagerDuty. It allows for detailed filtering and customization of the analysis, enabling users to gain insights into incident patterns, response time...
Aggregate incident metrics with filters
Retrieves and aggregates metrics for incidents across all services in PagerDuty. This endpoint allows for extensive filtering and customization of incident data, enabling detailed analysis of operational performance. It's particularly us...
Associate service dependencies
Associates multiple service dependencies in PagerDuty, allowing you to define relationships between supporting and dependent services. This endpoint is used to establish a hierarchical structure of services, which is crucial for effectiv...
Associate team with automation action
This endpoint associates a specific team with an automation action in PagerDuty. It allows you to link a team to an automated workflow, enabling better organization and management of automation actions within your incident response proce...
Audit escalation policy records
Retrieves the audit records for a specific escalation policy in PagerDuty. This endpoint allows users to access a detailed history of changes made to the escalation policy, including modifications to escalation rules, associated services...
What your agent does in Slack
Add call participants
Registers new participants added to a Slack call.
Add emoji
Adds a custom emoji to a Slack workspace given a unique name and an image URL; subject to workspace emoji limits.
Add an emoji alias
Adds an alias for an existing custom emoji in a Slack Enterprise Grid organization.
Add Enterprise user to workspace
Adds an Enterprise user to a workspace. Use when you need to assign an existing Enterprise Grid user to a specific workspace with optional guest restrictions.
Add reaction to message
Adds a specified emoji reaction to an existing message in a Slack channel, identified by its timestamp; does not remove or retrieve reactions.
Add a remote file
Adds a reference to an external file (e.g., Google Drive, Dropbox) to Slack for discovery and sharing, requiring a unique `external_id` and an `external_url` accessible by Slack.
How it works
Tell the agent what you want to happen between Pagerduty and Slack, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from Pagerduty, works out what to do, and runs the matching action in Slack without you mapping a single field.
You can have it run once, on a schedule, or whenever something changes. Ask it for a status any time and it reads the latest from both apps back to you in the same chat.
Common questions about Pagerduty and Slack
- How do I connect Pagerduty and Slack to Operator?
- You authorize Pagerduty and Slack once each from your Operator dashboard. Operator holds both connections and refreshes the access tokens for you, so your agent keeps working across them without you signing in again.
- What can my agent do across Pagerduty and Slack?
- Tell it the job and it moves between Pagerduty and Slack as one task, choosing which actions to run on each side. There is nothing to map and no trigger to configure; you give instructions the way you would to a person.
- Can my agent keep Pagerduty and Slack in sync?
- Yes. It can watch Pagerduty and act in Slack, or keep both in step, reading from one and running the matching update in the other. This runs on demand when you ask or on a schedule you set.
- Do I need to build a workflow or write code?
- No. There is no workflow to build, no fields to map, and no API keys to paste. Operator manages both connections, and you give the agent instructions in plain language.
Pagerduty and Slack integrations
Put your agent on Pagerduty and Slack
Sign in, connect both apps, and hand your agent the work. The same setup reaches every app in the catalog. Your first week is free.
Try for free