PagerDuty + ServiceNow
Connect PagerDuty and ServiceNow to Unify Incident Response and IT Service Management
Automate the bridge between real-time alerting and enterprise ITSM so your teams resolve incidents faster and keep every record in sync.
Why integrate PagerDuty and ServiceNow?
PagerDuty and ServiceNow are two of the most widely adopted platforms in enterprise IT operations — PagerDuty handles real-time on-call alerting and incident escalation, while ServiceNow is the system of record for IT service management, change management, and CMDB. Together, they cover the full incident lifecycle, from first alert to post-incident review. Integrating them closes the gap between detection and documentation that causes ticket duplication, missed SLAs, and siloed visibility.
Automate & integrate PagerDuty & ServiceNow
Use case
Auto-Create ServiceNow Incidents from PagerDuty Alerts
Whenever PagerDuty triggers a new incident above a defined severity threshold, tray.ai automatically creates a corresponding ServiceNow incident with all relevant metadata: impacted service, alert source, priority, and assignee group. On-call engineers don't have to open tickets manually during active incidents, which cuts lag and ensures every outage has a documented ITSM record from the moment it's detected.
Use case
Bidirectional Incident Status Synchronization
Keep PagerDuty and ServiceNow incident states aligned by syncing status changes in both directions. When a ServiceNow incident is resolved or closed by an ITSM analyst, tray.ai automatically resolves the corresponding PagerDuty alert, and vice versa. This two-way sync prevents ghost alerts, cuts notification fatigue, and ensures neither platform shows stale open incidents.
Use case
Escalate High-Priority ServiceNow Tickets to PagerDuty On-Call
When a critical or high-priority ServiceNow ticket is created or escalated — especially outside business hours — tray.ai can automatically trigger a PagerDuty alert and route it to the right on-call engineer based on ServiceNow's assignment group or CI ownership. Urgent ITSM requests get immediate human attention without manual handoffs between the service desk and engineering.
Use case
Sync PagerDuty Postmortems to ServiceNow Problem Records
After a major PagerDuty incident is resolved, tray.ai can automatically generate a ServiceNow Problem record populated with data from the PagerDuty postmortem: timeline, contributing services, responders, and root cause notes. The handoff from incident response to problem management happens without anyone having to remember to do it.
Use case
PagerDuty Maintenance Windows Triggered by ServiceNow Change Requests
When a ServiceNow change request is approved and scheduled, tray.ai can automatically create a PagerDuty maintenance window for the affected services during the change window. Expected alerts get suppressed, false-positive pages stop bothering on-call teams, and ServiceNow still has a clear audit trail.
Use case
Enrich PagerDuty Alerts with ServiceNow CMDB Data
When a PagerDuty incident is triggered, tray.ai can query the ServiceNow CMDB to fetch relevant configuration item (CI) details — owning team, environment, upstream dependencies, support contacts — and append them directly to the PagerDuty incident as custom context. On-call responders get richer situational awareness without switching tools during an active incident.
Use case
Automated SLA Breach Escalation Across Both Platforms
tray.ai can monitor ServiceNow SLA timers and automatically escalate incidents to PagerDuty when a resolution or response SLA is at risk of breaching. If a PagerDuty incident exceeds a defined acknowledgment time, tray.ai can also escalate the linked ServiceNow ticket priority. Both systems stay aligned, and costly SLA violations become avoidable rather than inevitable.
Get started with PagerDuty & ServiceNow integration today
PagerDuty & ServiceNow Challenges
What challenges are there when working with PagerDuty & ServiceNow and how will using Tray.ai help?
Challenge
Keeping Incident States in Sync Across Both Platforms
PagerDuty and ServiceNow each have their own incident state models — acknowledged, triggered, and resolved in PagerDuty versus new, in-progress, on-hold, and resolved in ServiceNow. Without a reliable integration layer, state changes in one system don't show up in the other, and teams lose track of what's actively being worked and what's already closed.
How Tray.ai Can Help:
tray.ai provides a flexible mapping layer that translates state transitions between PagerDuty and ServiceNow using conditional logic. Custom field mappings and workflow branches let teams define exactly how each state in one platform maps to the other, with idempotency checks to prevent duplicate updates or infinite sync loops.
Challenge
Avoiding Duplicate Ticket Creation
When multiple monitoring tools feed into PagerDuty and ServiceNow independently, the same underlying issue can easily spawn multiple tickets in ServiceNow or multiple alerts in PagerDuty. That fragments response efforts and makes it hard to know which record is authoritative.
How Tray.ai Can Help:
tray.ai workflows include deduplication logic that checks for existing open records in ServiceNow before creating new ones, using alert fingerprints, service identifiers, or custom correlation IDs. This keeps a one-to-one relationship between PagerDuty alerts and ServiceNow tickets throughout the incident lifecycle.
Challenge
Mapping Organizational Structures Between Systems
PagerDuty routes alerts through services, escalation policies, and on-call schedules. ServiceNow uses assignment groups, business services, and configuration items. These models rarely line up cleanly out of the box, which makes automatic routing difficult without manual intervention.
How Tray.ai Can Help:
tray.ai supports dynamic lookup tables and configurable mapping logic that translate PagerDuty service names to ServiceNow assignment groups and CIs. Those mappings can live in a connected data store or spreadsheet and get updated without redeploying the workflow, so operations teams control their own routing rules.
Challenge
Handling High-Volume Alert Storms Without Overloading ServiceNow
During major incidents, PagerDuty can generate dozens or hundreds of related alerts in a short window. If each one creates a ServiceNow incident, the service desk gets flooded with duplicates and can't identify the root issue — exactly the wrong outcome when things are already on fire.
How Tray.ai Can Help:
tray.ai workflows can implement alert aggregation and throttling logic — grouping related PagerDuty alerts under a single parent ServiceNow incident, applying rate limiting, or using PagerDuty's incident merge data to consolidate before passing anything through to ServiceNow. The service desk gets actionable, consolidated records instead of raw alert noise.
Challenge
Maintaining Audit Trails Across Both Systems for Compliance
Regulated industries need complete audit trails showing when an incident was detected, who responded, what actions were taken, and when it was resolved — across both the alerting platform and the ITSM system of record. Manual integration leaves gaps that create real compliance risk during audits.
How Tray.ai Can Help:
tray.ai logs every workflow execution and data transformation step, creating a transparent audit trail of everything passed between PagerDuty and ServiceNow. Workflows can also automatically append timestamped notes to ServiceNow records at each step — alert received, acknowledged, escalated, resolved — so the full incident history lives in the ITSM system where auditors expect to find it.
Start using our pre-built PagerDuty & ServiceNow templates today
Start from scratch or use one of our pre-built PagerDuty & ServiceNow templates to quickly solve your most common use cases.
PagerDuty & ServiceNow Templates
Find pre-built PagerDuty & ServiceNow solutions for common use cases
Template
PagerDuty Incident to ServiceNow Incident — Auto-Create and Sync
Automatically creates a new ServiceNow incident when a PagerDuty incident fires, maps severity and priority fields, and keeps both records in sync through the incident lifecycle until resolution and closure.
Steps:
- Listen for PagerDuty incident.triggered webhook event
- Map PagerDuty severity, service name, and alert details to ServiceNow incident fields
- Create a new ServiceNow incident via REST API and store the sys_id
- Listen for subsequent PagerDuty state changes (acknowledged, resolved)
- Update the ServiceNow incident state and resolution notes accordingly
Connectors Used: PagerDuty, ServiceNow
Template
ServiceNow Critical Ticket to PagerDuty Alert
Monitors ServiceNow for newly created or escalated P1/P2 incidents and automatically triggers a PagerDuty alert routed to the correct on-call schedule based on assignment group mapping.
Steps:
- Poll ServiceNow or receive webhook for new/updated incidents with priority P1 or P2
- Look up the corresponding PagerDuty service and escalation policy from assignment group
- Create a PagerDuty incident via API with enriched details from the ServiceNow record
- Store the PagerDuty incident ID back on the ServiceNow record for bidirectional tracking
Connectors Used: ServiceNow, PagerDuty
Template
ServiceNow Change Request to PagerDuty Maintenance Window
When a ServiceNow change request moves to an approved and scheduled state, this template automatically opens a PagerDuty maintenance window for the affected service to suppress alerts during the planned maintenance period.
Steps:
- Detect ServiceNow change request state change to 'Scheduled' or 'Implement'
- Extract the planned start time, end time, and affected CI from the change record
- Map the CI to the corresponding PagerDuty service using a lookup table
- Create a PagerDuty maintenance window via API for the mapped service and time window
- Log the maintenance window ID back to the ServiceNow change record
Connectors Used: ServiceNow, PagerDuty
Template
PagerDuty Postmortem to ServiceNow Problem Record
After a major PagerDuty incident is marked as resolved, this template extracts postmortem data and creates a structured ServiceNow Problem record to drive formal root cause analysis and long-term remediation tracking.
Steps:
- Trigger on PagerDuty incident resolution for incidents above a defined urgency threshold
- Retrieve incident details, timeline, and postmortem notes from PagerDuty API
- Create a new ServiceNow Problem record with root cause, impact, and affected services
- Link the ServiceNow Problem to the originating incident record via relationship
- Notify the problem management team in ServiceNow with a summary notification
Connectors Used: PagerDuty, ServiceNow
Template
CMDB Enrichment — Append ServiceNow CI Data to PagerDuty Incidents
Enriches active PagerDuty incidents with ServiceNow CMDB configuration item details, injecting ownership, environment, and dependency information as incident notes for faster on-call triage.
Steps:
- Detect new PagerDuty incident via webhook
- Extract the affected service name or CI identifier from the PagerDuty payload
- Query ServiceNow CMDB for the matching configuration item and its related attributes
- Format enrichment data (owner, environment, dependencies, support contacts) as a note
- Add the enrichment note to the PagerDuty incident via the API
Connectors Used: PagerDuty, ServiceNow
Template
SLA Breach Risk — ServiceNow to PagerDuty Escalation
Proactively monitors ServiceNow SLA timers and triggers a PagerDuty alert when an incident is approaching a breach threshold, so on-call engineers can intervene before the SLA window closes.
Steps:
- Scheduled tray.ai workflow polls ServiceNow for open incidents nearing SLA breach
- Filter incidents where SLA percentage elapsed exceeds configured warning threshold
- Verify no existing PagerDuty alert is already open for the incident to prevent duplicates
- Create a PagerDuty incident with SLA breach context and urgency set to high
- Update the ServiceNow incident with a note confirming escalation was triggered
Connectors Used: ServiceNow, PagerDuty