PagerDuty + Slack
Connect PagerDuty and Slack to Speed Up Incident Response
Get critical alerts, on-call updates, and incident workflows into Slack so your team can act fast and stay in sync.
Why integrate PagerDuty and Slack?
PagerDuty and Slack are two tools that operations, engineering, and DevOps teams live in every day — one to detect and route incidents, the other to talk and coordinate in real time. When they work together, the gap between an alert firing and a team responding shrinks fast. Integrating PagerDuty with Slack through tray.ai means incidents surface instantly in the right channels, stakeholders stay informed without chasing status updates, and responders can take action without switching tabs.
Automate & integrate PagerDuty & Slack
Use case
Real-Time Incident Alerts in Slack
When PagerDuty triggers a new incident, tray.ai automatically posts a formatted alert to the relevant Slack channel, including severity level, affected service, and a direct link to the incident. On-call engineers get immediate visibility without monitoring a separate dashboard. Teams can configure routing rules so P1 incidents go to a dedicated war room while lower-severity issues land in a general ops channel.
Use case
Automatic Incident War Room Creation
For high-severity incidents, tray.ai can automatically create a dedicated Slack channel — named after the incident ID and service — and invite the relevant on-call responders and stakeholders. The team gets a focused, timestamped space to coordinate without cluttering existing channels. When the incident is resolved, tray.ai can archive the channel and post a summary back to the main ops channel.
Use case
Two-Way Incident Acknowledgment and Status Updates
Responders can acknowledge, escalate, or resolve PagerDuty incidents directly from Slack using interactive buttons, without logging into PagerDuty. tray.ai syncs these status changes back to PagerDuty in real time, keeping both platforms consistent. This cuts the friction out of the first critical minutes of incident response, when every second counts.
Use case
On-Call Schedule and Escalation Notifications
tray.ai can pull the current on-call schedule from PagerDuty and post weekly or daily summaries to a designated Slack channel, so the whole team knows who's responsible at any given time. When an incident escalates to a secondary responder, tray.ai can trigger Slack DMs or channel alerts so nothing slips through.
Use case
Stakeholder Incident Status Broadcasts
Not everyone who needs incident visibility is in the war room. tray.ai can monitor PagerDuty incident status changes and automatically post updates to a leadership or company-wide Slack channel at each stage — triggered, acknowledged, resolved — with plain-language summaries. Executives and cross-functional teams stay informed without pulling engineers away from the fix.
Use case
Post-Incident Resolution Summaries
When PagerDuty marks an incident as resolved, tray.ai can automatically compile a resolution summary — including duration, responders involved, and timeline — and post it to Slack. Teams get an immediate debrief without waiting for a formal post-mortem, and that institutional knowledge lives in Slack where teams already communicate.
Use case
Scheduled On-Call Handoff Reminders
tray.ai can monitor PagerDuty schedule transitions and automatically send a Slack message to both the outgoing and incoming on-call engineer when a handoff is approaching. The message can include open incidents, recent alerts, and key runbook links, so active issues don't fall through the cracks during a rotation change.
Get started with PagerDuty & Slack integration today
PagerDuty & Slack Challenges
What challenges are there when working with PagerDuty & Slack and how will using Tray.ai help?
Challenge
Mapping PagerDuty Users to Slack Users Reliably
PagerDuty and Slack maintain separate user directories, and email addresses or display names may not match perfectly across both systems. Without a reliable mapping, automated DMs and war room invitations can fail silently or reach the wrong person — a dangerous gap during a live incident.
How Tray.ai Can Help:
tray.ai has a flexible data mapping layer that cross-references PagerDuty user attributes against Slack user lookups via the Slack API, using email as a common key. Custom logic handles edge cases like service accounts or users with inconsistent profile data, so the right person always gets the right message.
Challenge
Handling High Alert Volume Without Flooding Slack
During a system-wide outage, PagerDuty can trigger dozens or hundreds of related incidents in a short window. Posting each one individually to Slack creates noise that obscures the real situation, causes alert fatigue, and makes the channel unusable for actual coordination.
How Tray.ai Can Help:
tray.ai workflows can implement deduplication and grouping logic — aggregating related alerts into a single Slack message, applying time-window batching, and suppressing child incidents when a parent incident already exists. Slack channels stay actionable even during major outage events.
Challenge
Keeping Slack Messages Updated as Incident Status Changes
Posting a new Slack message for every PagerDuty status change — triggered, acknowledged, resolved — creates a noisy, hard-to-follow thread. Teams need a single, updating message that reflects the current state of an incident rather than a flood of new notifications.
How Tray.ai Can Help:
tray.ai stores the Slack message timestamp returned when the initial alert is posted, then uses Slack's message update API to edit that original message in place whenever PagerDuty status changes. Teams get a single, always-current incident card in Slack without the noise.
Challenge
Respecting Escalation Policy Complexity in Routing Logic
PagerDuty escalation policies can be multi-tiered, service-specific, and time-sensitive. Translating that complexity into Slack routing rules — the right channel, the right people, at the right time — is hard to maintain manually and tends to break as teams and services evolve.
How Tray.ai Can Help:
tray.ai workflows dynamically query PagerDuty's API at runtime to retrieve current escalation policy details rather than relying on hardcoded routing rules. Slack routing always reflects the live state of PagerDuty, automatically adapting as on-call schedules rotate or policies are updated.
Challenge
Archiving and Auditing Incident Conversations
Incident war room channels accumulate genuinely useful diagnostic information, but without a systematic process they pile up unarchived — or worse, get deleted and the institutional knowledge disappears. Post-mortem and compliance workflows often require a structured record of what happened and when.
How Tray.ai Can Help:
tray.ai can trigger an automated cleanup workflow when an incident resolves: export the Slack channel message history, post a final summary, archive the channel to keep Slack tidy, and optionally write the conversation record to a data store or ticketing system for long-term audit and post-mortem use.
Start using our pre-built PagerDuty & Slack templates today
Start from scratch or use one of our pre-built PagerDuty & Slack templates to quickly solve your most common use cases.
PagerDuty & Slack Templates
Find pre-built PagerDuty & Slack solutions for common use cases
Template
PagerDuty Incident to Slack Channel Alert
Automatically posts a formatted Slack message to a specified channel whenever a new PagerDuty incident is created, including severity, service name, incident summary, and a direct link to the PagerDuty incident page.
Steps:
- Trigger: PagerDuty webhook fires when a new incident is created
- Transform: tray.ai formats incident data into a structured Slack message block with severity color coding and key metadata
- Action: Post the formatted alert message to the designated Slack channel
Connectors Used: PagerDuty, Slack
Template
Auto-Create Slack War Room for High-Severity Incidents
When a P1 or P2 incident is triggered in PagerDuty, tray.ai automatically creates a new Slack channel named after the incident, invites the on-call responders from the PagerDuty escalation policy, and posts the initial incident details to kick off the response.
Steps:
- Trigger: PagerDuty incident created with severity P1 or P2
- Lookup: Retrieve the current on-call responders from PagerDuty escalation policy via API
- Action: Create a new Slack channel, invite responders, and post the incident brief with runbook links
Connectors Used: PagerDuty, Slack
Template
Slack-Based Incident Acknowledgment Back to PagerDuty
Adds interactive Acknowledge and Resolve buttons to PagerDuty alert messages posted in Slack, letting responders update incident status directly from Slack, with tray.ai syncing every action back to PagerDuty in real time.
Steps:
- Trigger: PagerDuty incident alert is posted to Slack with interactive action buttons
- Event: Responder clicks Acknowledge or Resolve button in Slack
- Action: tray.ai calls PagerDuty API to update incident status and posts a confirmation thread reply in Slack
Connectors Used: PagerDuty, Slack
Template
Weekly On-Call Schedule Digest to Slack
Every Monday morning, tray.ai fetches the current week's on-call schedule from PagerDuty and posts a structured digest to a team Slack channel, listing who is on call for each service and escalation tier.
Steps:
- Trigger: Scheduled workflow runs every Monday at 9 AM in the team's timezone
- Lookup: Fetch on-call schedule data from PagerDuty API for all relevant services
- Action: Format and post the weekly on-call digest to the designated Slack channel
Connectors Used: PagerDuty, Slack
Template
Incident Resolution Summary Posted to Slack
When a PagerDuty incident transitions to resolved, tray.ai automatically generates and posts a resolution summary to Slack, including total incident duration, responders involved, and a link to the full incident timeline for post-mortem review.
Steps:
- Trigger: PagerDuty webhook fires on incident status change to resolved
- Enrich: tray.ai fetches full incident details, log entries, and responder data from PagerDuty API
- Action: Post a structured resolution summary card to the ops Slack channel and optionally archive the war room channel
Connectors Used: PagerDuty, Slack
Template
PagerDuty Escalation Alert via Slack DM
When PagerDuty escalates an unacknowledged incident to a secondary responder, tray.ai sends a direct Slack message to that person with full incident context, so escalations don't get missed even if the responder isn't actively watching PagerDuty.
Steps:
- Trigger: PagerDuty escalation policy activates and notifies a new responder
- Lookup: Resolve the new responder's PagerDuty user profile to their Slack user ID
- Action: Send a direct Slack message to the escalated responder with incident details, severity, and a one-click link to acknowledge
Connectors Used: PagerDuty, Slack