Connectors / Integration
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.
Slack App + PagerDuty integration
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.
Modern engineering teams live in Slack, but incidents don't wait for anyone to check their dashboards. Connecting PagerDuty to Slack cuts the cognitive overhead of context-switching during an incident and brings alert triage, escalation, and resolution into one communication surface. Teams can acknowledge pages, reassign incidents, and update statuses without leaving Slack, while stakeholders get automatic, real-time visibility into what's happening. The result is faster incident response, less alert fatigue, and a clear audit trail of every action taken — no manual copy-paste required.
Automate & integrate Slack App + PagerDuty
Automating Slack App and PagerDuty business processes or integrating data is made easy with Tray.ai.
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.
- Instant visibility into new incidents across the entire team
- Alert cards with service name, severity, and escalation policy details
- Reduce mean time to acknowledge (MTTA) by surfacing alerts where engineers already work
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.
- One-click incident acknowledgment from the Slack notification itself
- Bidirectional status sync keeps PagerDuty and Slack aligned in real time
- Less context-switching during high-pressure incident response
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.
- No manual channel creation or invitations during active incidents
- All incident communication is centralized and searchable after resolution
- Faster team assembly means faster time to mitigate
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.
- Proactive Slack reminders reduce missed on-call handoffs
- Automated handoff summaries improve continuity between rotations
- Full team visibility into who is on call at any given time
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.
- Automated escalation prevents unacknowledged incidents from stalling
- Tagging the right escalation contact speeds up response without manual intervention
- Configurable thresholds let teams match escalation behavior to their SLAs
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.
- Automated incident summaries save engineering time on manual reporting
- Leadership and stakeholders get instant resolution visibility without needing PagerDuty access
- Structured data supports post-mortem processes and trend analysis
Challenges Tray.ai solves
Common obstacles when integrating Slack App and PagerDuty — and how Tray.ai handles them.
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 helps
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 helps
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 helps
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.
Templates
Pre-built workflows for Slack App and PagerDuty you can deploy in minutes.
PagerDuty Incident Alert to Slack Channel
Slack App 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.
High-Severity Incident War Room Channel Creator
Slack App 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.
Slack-Triggered PagerDuty Incident Acknowledgment
Slack App 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.
PagerDuty On-Call Shift Reminder to Slack DM
Slack App 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.
Resolved Incident Summary Reporter
Slack App 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.
Unacknowledged Incident Escalation Alert to Slack
Slack App 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.
How Tray.ai makes this work
Slack App + PagerDuty runs on the full Tray.ai platform
Intelligent iPaaS
Integrate and automate across 700+ connectors with visual workflows, error handling, and observability.
Learn more →Agent Builder
Build AI agents that read, write, and take action in Slack App and PagerDuty — with guardrails, audit, and human-in-the-loop.
Learn more →Agent Gateway
Expose Slack App + PagerDuty actions as governed MCP tools — observable, rate-limited, authenticated.
Learn more →Ship your Slack App + PagerDuty integration.
We'll walk through the exact integration you're imagining in a tailored demo.