Slack App + PagerDuty
Connect Slack and PagerDuty to Speed Up Incident Response
Get real-time alerts, on-call schedules, and incident management straight into your team's Slack workspace.
Why integrate Slack App and PagerDuty?
Slack and PagerDuty are two of the most-used tools in any DevOps or IT operations team's stack — one powers team communication, the other drives incident management and on-call workflows. When they run in isolation, engineers waste precious minutes switching between tabs during high-pressure outages. Integrating Slack with PagerDuty through tray.ai means every alert, acknowledgment, and resolution flows between both platforms automatically, keeping your team informed and your MTTR low.
Automate & integrate Slack App & PagerDuty
Use case
Real-Time PagerDuty Alert Notifications in Slack
Automatically post PagerDuty incident alerts to the right Slack channel the moment they're triggered. Engineers and on-call responders get actionable notifications — including severity, affected service, and a direct link to the incident — without needing to monitor PagerDuty directly. No critical alert slips through, even during off-hours.
Use case
Acknowledge and Resolve Incidents Directly from Slack
On-call engineers can acknowledge, escalate, or resolve PagerDuty incidents using interactive Slack buttons or slash commands — no trip to PagerDuty's UI needed. When an action is taken in Slack, the incident status in PagerDuty updates in real time, keeping both systems in sync. This cuts the time between alert and acknowledgment considerably.
Use case
Automated Incident War Room Channel Creation
When a high-severity PagerDuty incident fires, automatically spin up a dedicated Slack channel, invite the relevant on-call engineers and stakeholders, and post the full incident context as the first message. You get an organized communication hub for the incident with no manual setup. After resolution, the channel can be archived automatically and a post-mortem thread kicked off.
Use case
On-Call Schedule Reminders and Handoff Notifications
Automatically notify engineers in Slack when their on-call shift is about to begin or end, pulling schedule data directly from PagerDuty. Handoff messages can include a summary of open or recently resolved incidents, so rotations stay smooth. Teams can also post weekly on-call schedules to a dedicated Slack channel so everyone knows who's responsible.
Use case
Escalation Alerts When Incidents Go Unacknowledged
When a PagerDuty incident sits unacknowledged past a defined threshold, automatically post an escalation warning to a Slack channel and tag the next person in the escalation policy. This prevents critical incidents from stalling during busy periods or off-hours. Thresholds are configurable per escalation tier or service priority.
Use case
Post-Incident Summary Reports to Slack
Once a PagerDuty incident is resolved, automatically post a structured summary to a designated Slack channel — time to acknowledge, time to resolve, impacted services, and the responders involved. This creates an automatic record of every incident for leadership, SRE teams, and post-mortem tracking, and gives teams the data to spot patterns and prioritize reliability work.
Use case
Sync PagerDuty Maintenance Windows to Slack
When a maintenance window is scheduled or activated in PagerDuty, automatically notify relevant Slack channels so engineers and stakeholders know about planned suppression periods. This prevents confusion when alerts are intentionally silenced and keeps the broader team in the loop on scheduled maintenance. Notifications can include window duration, affected services, and the scheduling engineer.
Get started with Slack App & PagerDuty integration today
Slack App & PagerDuty Challenges
What challenges are there when working with Slack App & PagerDuty and how will using Tray.ai help?
Challenge
Alert Noise and Slack Channel Fatigue
Routing every PagerDuty alert to Slack without filtering can quickly bury channels in noise, causing engineers to tune out notifications entirely. Teams need routing based on severity, service, or team ownership to keep Slack worth checking.
How Tray.ai Can Help:
tray.ai's workflow logic lets you build conditional routing rules that filter and direct PagerDuty alerts based on severity level, impacted service, or escalation policy. Only the right alerts reach the right channels, so engineers aren't wading through noise to find what matters.
Challenge
Keeping Incident Status Bidirectionally in Sync
When engineers acknowledge or resolve an incident directly in PagerDuty's UI, Slack messages can go stale and show outdated status information — leading to real confusion about whether an incident is still active. Manually updating both systems is slow and error-prone when things are moving fast.
How Tray.ai Can Help:
tray.ai listens for PagerDuty webhook events in real time and automatically updates the corresponding Slack message, editing the original alert card to reflect the latest status, responder, and timestamps. Slack always shows the true state of every incident.
Challenge
Mapping PagerDuty Users to Slack Identities
PagerDuty and Slack maintain separate user directories, and matching responders between the two — especially for tagging, DMs, and war room invitations — requires reliable user mapping that doesn't break when email addresses or display names differ.
How Tray.ai Can Help:
tray.ai can maintain a user mapping lookup table or use shared email addresses to resolve PagerDuty user identities to their Slack user IDs at runtime. Mentions, DMs, and channel invitations always reach the right person without hardcoded mappings.
Challenge
Handling PagerDuty Webhook Reliability and Retries
PagerDuty webhooks can occasionally fail to deliver due to network issues, Slack rate limits, or temporary service disruptions. Without retry logic and error handling, critical incident notifications can be silently dropped — and no one finds out until it's too late.
How Tray.ai Can Help:
tray.ai includes built-in error handling, retry logic, and workflow monitoring to make sure webhook payloads are processed reliably. Failed steps are automatically retried, and teams can configure alerting on workflow failures so no incident notification is ever silently lost.
Challenge
Managing Multi-Team and Multi-Service Alert Routing
Large engineering organizations with multiple teams and dozens of services need fine-grained control over which PagerDuty alerts go to which Slack channels and which team members are tagged. Simple native integrations don't come close to handling that complexity.
How Tray.ai Can Help:
tray.ai supports sophisticated routing logic using PagerDuty service metadata, escalation policy names, and team assignments to dynamically determine the correct Slack channel and responder mentions for every alert. Routing rules can be updated centrally without code changes, giving operations teams full control over alert distribution at scale.
Start using our pre-built Slack App & PagerDuty templates today
Start from scratch or use one of our pre-built Slack App & PagerDuty templates to quickly solve your most common use cases.
Slack App & PagerDuty Templates
Find pre-built Slack App & PagerDuty solutions for common use cases
Template
PagerDuty Incident Alert to Slack Channel
Automatically posts a formatted Slack message to a specified channel whenever a new PagerDuty incident is triggered, including incident ID, severity, affected service, and a direct link to the incident in PagerDuty.
Steps:
- PagerDuty webhook triggers when a new incident is created
- tray.ai parses the incident payload to extract severity, service, and description
- Slack App posts a formatted alert message to the designated incident channel
Connectors Used: PagerDuty, Slack App
Template
High-Severity Incident War Room Channel Creator
When a PagerDuty incident with critical or high severity is triggered, this template automatically creates a new Slack channel named after the incident, invites all on-call responders from the PagerDuty escalation policy, and posts the full incident details as the pinned opening message.
Steps:
- PagerDuty webhook fires when a high-severity incident is opened
- tray.ai fetches on-call users from the relevant PagerDuty escalation policy
- Slack App creates a new incident channel, invites all responders, and pins incident context
Connectors Used: PagerDuty, Slack App
Template
Slack-Triggered PagerDuty Incident Acknowledgment
Adds interactive Acknowledge and Resolve buttons to PagerDuty alert messages in Slack. When a user clicks a button, tray.ai calls the PagerDuty API to update the incident status and posts a confirmation message back to the Slack thread.
Steps:
- Slack App captures the interactive button click from the alert message
- tray.ai identifies the incident ID and desired action from the payload
- PagerDuty API updates the incident status and Slack App confirms the action in-thread
Connectors Used: Slack App, PagerDuty
Template
PagerDuty On-Call Shift Reminder to Slack DM
Checks PagerDuty on-call schedules on a recurring basis and sends a personalized Slack direct message to each engineer 30 minutes before their shift begins, including any currently open incidents they'll inherit.
Steps:
- tray.ai runs on a scheduled trigger every 30 minutes
- PagerDuty API is queried to identify upcoming on-call shift transitions
- Slack App sends a personalized DM to the incoming on-call engineer with shift details and open incidents
Connectors Used: PagerDuty, Slack App
Template
Resolved Incident Summary Reporter
After a PagerDuty incident is resolved, automatically compiles a post-incident summary — including MTTA, MTTR, affected services, and responder list — and posts it as a formatted message to a designated Slack ops channel.
Steps:
- PagerDuty webhook triggers when an incident status changes to resolved
- tray.ai calculates MTTA and MTTR and compiles responder and service data
- Slack App posts a structured incident summary report to the ops or SRE channel
Connectors Used: PagerDuty, Slack App
Template
Unacknowledged Incident Escalation Alert to Slack
Monitors open PagerDuty incidents on a schedule and sends an escalation notification to a Slack channel — tagging the next-tier responder — if an incident has sat unacknowledged past a configurable time threshold.
Steps:
- tray.ai runs a scheduled check against open PagerDuty incidents at a defined interval
- tray.ai evaluates each incident's age against the configured acknowledgment threshold
- Slack App sends an escalation alert to the incident channel and tags the next escalation contact from PagerDuty
Connectors Used: PagerDuty, Slack App