PagerDuty
Manage and react to incidents in PagerDuty
Triggers
Section titled “Triggers” On Incident Listen to incident events
On Incident Annotated Listen to incident annotation events
On Incident Status Update Listen to incident status update events
Actions
Section titled “Actions” Acknowledge Incident Acknowledge an incident in PagerDuty
Annotate Incident Add a note to an existing incident in PagerDuty
Create Incident Create a new incident in PagerDuty
Escalate Incident Escalate an incident to a specific level (high-urgency only)
List Incidents Query PagerDuty to get a list of all open incidents (triggered and acknowledged)
List Log Entries List all log entries (audit trail) for a PagerDuty incident
List Notes List all notes (timeline entries) for a PagerDuty incident
Resolve Incident Resolve an incident in PagerDuty
Snooze Incident Snooze an acknowledged incident in PagerDuty
Update Incident Update an existing incident in PagerDuty
On Incident
Section titled “On Incident”The On Incident trigger starts a workflow execution when PagerDuty incident events occur.
Use Cases
Section titled “Use Cases”- Incident automation: Automate responses to incident events
- Notification workflows: Send notifications when incidents are triggered or resolved
- Integration workflows: Sync incidents with external systems
- Escalation handling: Handle incident escalations automatically
Configuration
Section titled “Configuration”- Service: Select the PagerDuty service to monitor
- Events: Select which incident events to listen for (triggered, acknowledged, resolved)
- Urgencies: Filter by urgency level (low, high) - leave empty to listen to all urgencies
Event Data
Section titled “Event Data”Each incident event includes:
- event: Event type (incident.triggered, incident.acknowledged, incident.resolved)
- incident: Complete incident information including title, description, urgency, status
- service: Service information
- assignments: Current incident assignments
Webhook Setup
Section titled “Webhook Setup”This trigger automatically sets up a PagerDuty webhook subscription when configured. The subscription is managed by SuperPlane and will be cleaned up when the trigger is removed.
Example Data
Section titled “Example Data”{ "data": { "agent": { "html_url": "https://acme.pagerduty.com/users/PLH1HKV", "id": "PLH1HKV", "self": "https://api.pagerduty.com/users/PLH1HKV", "summary": "Tenex Engineer", "type": "user_reference" }, "incident": { "assignees": [ { "html_url": "https://acme.pagerduty.com/users/PTUXL6G", "id": "PTUXL6G", "self": "https://api.pagerduty.com/users/PTUXL6G", "summary": "User 123", "type": "user_reference" } ], "conference_bridge": { "conference_number": "+1 1234123412,,987654321#", "conference_url": "https://example.com" }, "created_at": "2020-04-09T15:16:27Z", "escalation_policy": { "html_url": "https://acme.pagerduty.com/escalation_policies/PUS0KTE", "id": "PUS0KTE", "self": "https://api.pagerduty.com/escalation_policies/PUS0KTE", "summary": "Default", "type": "escalation_policy_reference" }, "html_url": "https://acme.pagerduty.com/incidents/PGR0VU2", "id": "PGR0VU2", "incident_key": "d3640fbd41094207a1c11e58e46b1662", "number": 2, "priority": { "html_url": "https://acme.pagerduty.com/account/incident_priorities", "id": "PSO75BM", "self": "https://api.pagerduty.com/priorities/PSO75BM", "summary": "P1", "type": "priority_reference" }, "reopened_at": "2020-10-02T18:45:22Z", "resolve_reason": null, "self": "https://api.pagerduty.com/incidents/PGR0VU2", "service": { "html_url": "https://acme.pagerduty.com/services/PF9KMXH", "id": "PF9KMXH", "self": "https://api.pagerduty.com/services/PF9KMXH", "summary": "API Service", "type": "service_reference" }, "status": "triggered", "teams": [ { "html_url": "https://acme.pagerduty.com/teams/PFCVPS0", "id": "PFCVPS0", "self": "https://api.pagerduty.com/teams/PFCVPS0", "summary": "Engineering", "type": "team_reference" } ], "title": "A little bump in the road", "type": "incident", "urgency": "high" } }, "timestamp": "2026-01-19T12:00:00Z", "type": "pagerduty.onIncident"}On Incident Annotated
Section titled “On Incident Annotated”The On Incident Annotated trigger starts a workflow execution when a note is added to a PagerDuty incident.
Use Cases
Section titled “Use Cases”- Note tracking: Track when notes are added to incidents
- Collaboration workflows: Trigger actions based on incident annotations
- Audit logging: Log all notes added to incidents
- Integration sync: Sync notes with external ticketing systems
Configuration
Section titled “Configuration”- Service: Select the PagerDuty service to monitor for incident annotations
Event Data
Section titled “Event Data”Each annotation event includes:
- agent: Information about who added the note
- incident: Complete incident information
Webhook Setup
Section titled “Webhook Setup”This trigger automatically sets up a PagerDuty webhook subscription when configured. The subscription is managed by SuperPlane and will be cleaned up when the trigger is removed.
Example Data
Section titled “Example Data”{ "data": { "agent": { "html_url": "https://acme.pagerduty.com/users/PLH1HKV", "id": "PLH1HKV", "self": "https://api.pagerduty.com/users/PLH1HKV", "summary": "Tenex Engineer", "type": "user_reference" }, "annotation": { "content": "Investigating the root cause. Initial analysis suggests a database connection timeout." }, "incident": { "assignees": [ { "html_url": "https://acme.pagerduty.com/users/PTUXL6G", "id": "PTUXL6G", "self": "https://api.pagerduty.com/users/PTUXL6G", "summary": "User 123", "type": "user_reference" } ], "created_at": "2020-04-09T15:16:27Z", "escalation_policy": { "html_url": "https://acme.pagerduty.com/escalation_policies/PUS0KTE", "id": "PUS0KTE", "self": "https://api.pagerduty.com/escalation_policies/PUS0KTE", "summary": "Default", "type": "escalation_policy_reference" }, "html_url": "https://acme.pagerduty.com/incidents/PGR0VU2", "id": "PGR0VU2", "incident_key": "d3640fbd41094207a1c11e58e46b1662", "number": 2, "self": "https://api.pagerduty.com/incidents/PGR0VU2", "service": { "html_url": "https://acme.pagerduty.com/services/PF9KMXH", "id": "PF9KMXH", "self": "https://api.pagerduty.com/services/PF9KMXH", "summary": "API Service", "type": "service_reference" }, "status": "acknowledged", "teams": [ { "html_url": "https://acme.pagerduty.com/teams/PFCVPS0", "id": "PFCVPS0", "self": "https://api.pagerduty.com/teams/PFCVPS0", "summary": "Engineering", "type": "team_reference" } ], "title": "A little bump in the road", "type": "incident", "urgency": "high" } }, "timestamp": "2026-01-19T12:00:00Z", "type": "pagerduty.incident.annotated"}On Incident Status Update
Section titled “On Incident Status Update”The On Incident Status Update trigger starts a workflow execution when PagerDuty incident status changes.
Use Cases
Section titled “Use Cases”- Status tracking: Track incident status changes and update systems
- Workflow automation: Trigger workflows when incidents are acknowledged or resolved
- Notification systems: Notify teams about status updates
- Integration workflows: Sync status changes with external systems
Configuration
Section titled “Configuration”- Service: Select the PagerDuty service to monitor for status updates
Event Data
Section titled “Event Data”Each status update event includes:
- event: Event type (incident.status_updated)
- incident: Complete incident information including current status
- status: New incident status
- service: Service information
- assignments: Current incident assignments
Webhook Setup
Section titled “Webhook Setup”This trigger automatically sets up a PagerDuty webhook subscription when configured. The subscription is managed by SuperPlane and will be cleaned up when the trigger is removed.
Example Data
Section titled “Example Data”{ "data": { "agent": { "html_url": "https://acme.pagerduty.com/users/PLH1HKV", "id": "PLH1HKV", "self": "https://api.pagerduty.com/users/PLH1HKV", "summary": "Tenex Engineer", "type": "user_reference" }, "incident": { "html_url": "https://acme.pagerduty.com/incidents/PGR0VU2", "id": "PGR0VU2", "self": "https://api.pagerduty.com/incidents/PGR0VU2", "summary": "A little bump in the road", "type": "incident_reference" }, "status_update": { "created_at": "2026-01-19T12:30:00Z", "id": "P1234567", "message": "We have identified the issue and are working on a fix.", "sender": { "html_url": "https://acme.pagerduty.com/users/PLH1HKV", "id": "PLH1HKV", "self": "https://api.pagerduty.com/users/PLH1HKV", "summary": "Tenex Engineer", "type": "user_reference" } } }, "timestamp": "2026-01-19T12:30:00Z", "type": "pagerduty.incident.status_update_published"}Acknowledge Incident
Section titled “Acknowledge Incident”The Acknowledge Incident component acknowledges an existing PagerDuty incident.
Use Cases
Section titled “Use Cases”- Incident response: Acknowledge an incident to stop escalations and indicate someone is working on it
- Automated acknowledgement: Automatically acknowledge incidents based on workflow conditions
- Integration workflows: Acknowledge incidents when related events occur in other systems
Configuration
Section titled “Configuration”- Incident ID: The ID of the incident to acknowledge (e.g., A12BC34567…)
- From Email: Email address of a valid PagerDuty user (required for App OAuth, optional for API tokens)
Behavior
Section titled “Behavior”When an incident is acknowledged, escalations are paused and the incident status changes to “acknowledged”. The incident will remain acknowledged until it is resolved or re-triggered.
Output
Section titled “Output”Returns the acknowledged incident object with all current information.
Example Output
Section titled “Example Output”{ "data": { "incident": { "assigned_via": "escalation_policy", "assignments": [ { "assignee": { "html_url": "https://subdomain.pagerduty.com/users/PXPGF42", "id": "PXPGF42", "self": "https://api.pagerduty.com/users/PXPGF42", "summary": "Earline Greenholt", "type": "user_reference" }, "at": "2015-11-10T00:31:52Z" } ], "created_at": "2015-10-06T21:30:42Z", "escalation_policy": { "html_url": "https://subdomain.pagerduty.com/escalation_policies/PT20YPA", "id": "PT20YPA", "self": "https://api.pagerduty.com/escalation_policies/PT20YPA", "summary": "Another Escalation Policy", "type": "escalation_policy_reference" }, "first_trigger_log_entry": { "html_url": "https://subdomain.pagerduty.com/incidents/PT4KHLK/log_entries/Q02JTSNZWHSEKV", "id": "Q02JTSNZWHSEKV", "self": "https://api.pagerduty.com/log_entries/Q02JTSNZWHSEKV?incident_id=PT4KHLK", "summary": "Triggered through the API", "type": "trigger_log_entry_reference" }, "html_url": "https://subdomain.pagerduty.com/incidents/PT4KHLK", "id": "PT4KHLK", "incident_key": "baf7cf21b1da41b4b0221008339ff357", "incident_number": 1234, "last_status_change_at": "2015-10-06T21:38:23Z", "last_status_change_by": { "html_url": "https://subdomain.pagerduty.com/users/PXPGF42", "id": "PXPGF42", "self": "https://api.pagerduty.com/users/PXPGF42", "summary": "Earline Greenholt", "type": "user_reference" }, "priority": { "id": "P53ZZH5", "self": "https://api.pagerduty.com/priorities/P53ZZH5", "summary": "P2", "type": "priority_reference" }, "resolved_at": null, "self": "https://api.pagerduty.com/incidents/PT4KHLK", "service": { "html_url": "https://subdomain.pagerduty.com/service-directory/PWIXJZS", "id": "PWIXJZS", "self": "https://api.pagerduty.com/services/PWIXJZS", "summary": "My Mail Service", "type": "service_reference" }, "status": "acknowledged", "summary": "[#1234] The server is on fire.", "teams": [ { "html_url": "https://subdomain.pagerduty.com/teams/PQ9K7I8", "id": "PQ9K7I8", "self": "https://api.pagerduty.com/teams/PQ9K7I8", "summary": "Engineering", "type": "team_reference" } ], "title": "The server is on fire.", "type": "incident", "updated_at": "2015-10-06T21:40:23Z", "urgency": "high" } }, "timestamp": "2026-01-19T12:00:00Z", "type": "pagerduty.incident"}Annotate Incident
Section titled “Annotate Incident”The Annotate Incident component adds a note to an existing PagerDuty incident.
Use Cases
Section titled “Use Cases”- Status updates: Add progress updates to an incident
- Investigation notes: Document findings during incident investigation
- Handoff information: Leave notes for the next responder
- Resolution details: Document the root cause and resolution steps
Configuration
Section titled “Configuration”- Incident ID: The ID of the incident to annotate (e.g., A12BC34567…)
- Content: The note content to add to the incident (supports expressions)
- From Email: Email address of a valid PagerDuty user (required for App OAuth, optional for API tokens)
Output
Section titled “Output”Returns the incident object with all current information.
Example Output
Section titled “Example Output”{ "data": { "incident": { "assigned_via": "escalation_policy", "assignments": [ { "assignee": { "html_url": "https://subdomain.pagerduty.com/users/PXPGF42", "id": "PXPGF42", "self": "https://api.pagerduty.com/users/PXPGF42", "summary": "Earline Greenholt", "type": "user_reference" }, "at": "2015-11-10T00:31:52Z" } ], "created_at": "2015-10-06T21:30:42Z", "escalation_policy": { "html_url": "https://subdomain.pagerduty.com/escalation_policies/PT20YPA", "id": "PT20YPA", "self": "https://api.pagerduty.com/escalation_policies/PT20YPA", "summary": "Another Escalation Policy", "type": "escalation_policy_reference" }, "first_trigger_log_entry": { "html_url": "https://subdomain.pagerduty.com/incidents/PT4KHLK/log_entries/Q02JTSNZWHSEKV", "id": "Q02JTSNZWHSEKV", "self": "https://api.pagerduty.com/log_entries/Q02JTSNZWHSEKV?incident_id=PT4KHLK", "summary": "Triggered through the API", "type": "trigger_log_entry_reference" }, "html_url": "https://subdomain.pagerduty.com/incidents/PT4KHLK", "id": "PT4KHLK", "incident_key": "baf7cf21b1da41b4b0221008339ff357", "incident_number": 1234, "incident_type": { "name": "major_incident" }, "last_status_change_at": "2015-10-06T21:38:23Z", "last_status_change_by": { "html_url": "https://subdomain.pagerduty.com/users/PXPGF42", "id": "PXPGF42", "self": "https://api.pagerduty.com/users/PXPGF42", "summary": "Earline Greenholt", "type": "user_reference" }, "priority": { "id": "P53ZZH5", "self": "https://api.pagerduty.com/priorities/P53ZZH5", "summary": "P2", "type": "priority_reference" }, "resolved_at": null, "self": "https://api.pagerduty.com/incidents/PT4KHLK", "service": { "html_url": "https://subdomain.pagerduty.com/service-directory/PWIXJZS", "id": "PWIXJZS", "self": "https://api.pagerduty.com/services/PWIXJZS", "summary": "My Mail Service", "type": "service_reference" }, "status": "acknowledged", "summary": "[#1234] The server is on fire.", "teams": [ { "html_url": "https://subdomain.pagerduty.com/teams/PQ9K7I8", "id": "PQ9K7I8", "self": "https://api.pagerduty.com/teams/PQ9K7I8", "summary": "Engineering", "type": "team_reference" } ], "title": "The server is on fire.", "type": "incident", "updated_at": "2015-10-06T21:40:23Z", "urgency": "high" } }, "timestamp": "2026-01-19T12:00:00Z", "type": "pagerduty.incident"}Create Incident
Section titled “Create Incident”The Create Incident component creates a new incident in PagerDuty.
Use Cases
Section titled “Use Cases”- Alert escalation: Create incidents from monitoring alerts
- Error tracking: Automatically create incidents when errors are detected
- Manual incident creation: Create incidents from workflow events
- Integration workflows: Create incidents from external system events
Configuration
Section titled “Configuration”- Title: A succinct description of the incident (required, supports expressions)
- Description: Additional details about the incident (optional, supports expressions)
- Urgency: Incident urgency level (high or low)
- Service: Select the PagerDuty service to create the incident in
- From Email: Email address of a valid PagerDuty user (required for App OAuth, optional for API tokens)
Output
Section titled “Output”Returns the created incident object including:
- id: Incident ID
- incident_number: Human-readable incident number
- status: Current incident status
- urgency: Incident urgency
- service: Service information
- created_at: Incident creation timestamp
Example Output
Section titled “Example Output”{ "data": { "incident": { "assigned_via": "escalation_policy", "assignments": [ { "assignee": { "html_url": "https://subdomain.pagerduty.com/users/PXPGF42", "id": "PXPGF42", "self": "https://api.pagerduty.com/users/PXPGF42", "summary": "Earline Greenholt", "type": "user_reference" }, "at": "2015-11-10T00:31:52Z" } ], "created_at": "2015-10-06T21:30:42Z", "escalation_policy": { "html_url": "https://subdomain.pagerduty.com/escalation_policies/PT20YPA", "id": "PT20YPA", "self": "https://api.pagerduty.com/escalation_policies/PT20YPA", "summary": "Another Escalation Policy", "type": "escalation_policy_reference" }, "first_trigger_log_entry": { "html_url": "https://subdomain.pagerduty.com/incidents/PT4KHLK/log_entries/Q02JTSNZWHSEKV", "id": "Q02JTSNZWHSEKV", "self": "https://api.pagerduty.com/log_entries/Q02JTSNZWHSEKV?incident_id=PT4KHLK", "summary": "Triggered through the API", "type": "trigger_log_entry_reference" }, "html_url": "https://subdomain.pagerduty.com/incidents/PT4KHLK", "id": "PT4KHLK", "incident_key": "baf7cf21b1da41b4b0221008339ff357", "incident_number": 1234, "incident_type": { "name": "major_incident" }, "last_status_change_at": "2015-10-06T21:38:23Z", "last_status_change_by": { "html_url": "https://subdomain.pagerduty.com/users/PXPGF42", "id": "PXPGF42", "self": "https://api.pagerduty.com/users/PXPGF42", "summary": "Earline Greenholt", "type": "user_reference" }, "priority": { "id": "P53ZZH5", "self": "https://api.pagerduty.com/priorities/P53ZZH5", "summary": "P2", "type": "priority_reference" }, "resolved_at": null, "self": "https://api.pagerduty.com/incidents/PT4KHLK", "service": { "html_url": "https://subdomain.pagerduty.com/service-directory/PWIXJZS", "id": "PWIXJZS", "self": "https://api.pagerduty.com/services/PWIXJZS", "summary": "My Mail Service", "type": "service_reference" }, "status": "triggered", "summary": "[#1234] The server is on fire.", "teams": [ { "html_url": "https://subdomain.pagerduty.com/teams/PQ9K7I8", "id": "PQ9K7I8", "self": "https://api.pagerduty.com/teams/PQ9K7I8", "summary": "Engineering", "type": "team_reference" } ], "title": "The server is on fire.", "type": "incident", "updated_at": "2015-10-06T21:40:23Z", "urgency": "high" } }, "timestamp": "2026-01-19T12:00:00Z", "type": "pagerduty.incident"}Escalate Incident
Section titled “Escalate Incident”The Escalate Incident component escalates an existing PagerDuty incident to a specific escalation level within its current escalation policy.
Important: High-Urgency Incidents Only
Section titled “Important: High-Urgency Incidents Only”This action only works on high-urgency incidents. Low-urgency incidents cannot be escalated in PagerDuty. If you need to reassign a low-urgency incident, use the “Reassign Escalation Policy” action instead.
What is Escalation?
Section titled “What is Escalation?”In PagerDuty, an escalation policy defines a chain of responders:
- Level 1: Primary on-call (e.g., the assigned engineer)
- Level 2: Secondary responder (e.g., team lead)
- Level 3: Tertiary responder (e.g., manager)
- And so on…
Escalating an incident moves it to a higher level, notifying the responders at that level immediately instead of waiting for the automatic escalation timeout.
Use Cases
Section titled “Use Cases”- Manual escalation: Escalate when the current responder cannot resolve the issue
- Automated escalation: Automatically escalate based on workflow conditions (e.g., incident age)
- Skip levels: Jump directly to a higher level for critical situations
Configuration
Section titled “Configuration”- Incident ID: The ID of the incident to escalate (e.g., A12BC34567…)
- Escalation Level: The level to escalate to (1-10). This is the level number within the incident’s current escalation policy.
- From Email: Email address of a valid PagerDuty user (required for App OAuth, optional for API tokens)
Output
Section titled “Output”Returns the escalated incident object with all current information.
Example Output
Section titled “Example Output”{ "data": { "incident": { "assigned_via": "escalation_policy", "assignments": [ { "assignee": { "html_url": "https://subdomain.pagerduty.com/users/PUSER02", "id": "PUSER02", "self": "https://api.pagerduty.com/users/PUSER02", "summary": "Manager Smith", "type": "user_reference" }, "at": "2015-10-06T21:42:00Z" } ], "created_at": "2015-10-06T21:30:42Z", "escalation_policy": { "html_url": "https://subdomain.pagerduty.com/escalation_policies/PT20YPA", "id": "PT20YPA", "self": "https://api.pagerduty.com/escalation_policies/PT20YPA", "summary": "Another Escalation Policy", "type": "escalation_policy_reference" }, "first_trigger_log_entry": { "html_url": "https://subdomain.pagerduty.com/incidents/PT4KHLK/log_entries/Q02JTSNZWHSEKV", "id": "Q02JTSNZWHSEKV", "self": "https://api.pagerduty.com/log_entries/Q02JTSNZWHSEKV?incident_id=PT4KHLK", "summary": "Triggered through the API", "type": "trigger_log_entry_reference" }, "html_url": "https://subdomain.pagerduty.com/incidents/PT4KHLK", "id": "PT4KHLK", "incident_key": "baf7cf21b1da41b4b0221008339ff357", "incident_number": 1234, "last_status_change_at": "2015-10-06T21:42:00Z", "last_status_change_by": { "html_url": "https://subdomain.pagerduty.com/users/PXPGF42", "id": "PXPGF42", "self": "https://api.pagerduty.com/users/PXPGF42", "summary": "Earline Greenholt", "type": "user_reference" }, "priority": { "id": "P53ZZH5", "self": "https://api.pagerduty.com/priorities/P53ZZH5", "summary": "P2", "type": "priority_reference" }, "resolved_at": null, "self": "https://api.pagerduty.com/incidents/PT4KHLK", "service": { "html_url": "https://subdomain.pagerduty.com/service-directory/PWIXJZS", "id": "PWIXJZS", "self": "https://api.pagerduty.com/services/PWIXJZS", "summary": "My Mail Service", "type": "service_reference" }, "status": "triggered", "summary": "[#1234] The server is on fire.", "teams": [ { "html_url": "https://subdomain.pagerduty.com/teams/PQ9K7I8", "id": "PQ9K7I8", "self": "https://api.pagerduty.com/teams/PQ9K7I8", "summary": "Engineering", "type": "team_reference" } ], "title": "The server is on fire.", "type": "incident", "updated_at": "2015-10-06T21:42:00Z", "urgency": "high" } }, "timestamp": "2026-01-19T12:00:00Z", "type": "pagerduty.incident"}List Incidents
Section titled “List Incidents”The List Incidents component queries PagerDuty for open incidents and routes execution based on urgency levels.
Use Cases
Section titled “Use Cases”- Health checks: Check for active incidents and route based on severity
- Incident monitoring: Monitor incident status across services
- Automated response: Trigger workflows based on incident presence
- Reporting: Collect incident data for reporting or analysis
Configuration
Section titled “Configuration”- Services: Optional list of services to filter incidents (leave empty to get incidents from all services)
Output Channels
Section titled “Output Channels”- Clear: No open incidents found
- Low: Only low urgency incidents found
- High: One or more high urgency incidents found
Output
Section titled “Output”Returns a list of open incidents with:
- id: Incident ID
- incident_number: Human-readable incident number
- status: Incident status (triggered, acknowledged)
- urgency: Incident urgency (low, high)
- title: Incident title
- service: Service information
- assignments: Current assignments
Example Output
Section titled “Example Output”{ "data": { "incidents": [ { "acknowledgements": [], "assignments": [ { "assignee": { "html_url": "https://example.pagerduty.com/users/PUSER01", "id": "PUSER01", "summary": "John Doe", "type": "user_reference" }, "at": "2024-01-15T12:00:00Z" } ], "created_at": "2024-01-15T12:00:00Z", "description": "The production server is experiencing critical issues", "escalation_policy": { "html_url": "https://example.pagerduty.com/escalation_policies/PABCDEF", "id": "PABCDEF", "summary": "Default Escalation Policy", "type": "escalation_policy_reference" }, "html_url": "https://example.pagerduty.com/incidents/PT4KHLK", "id": "PT4KHLK", "incident_number": 1234, "priority": { "id": "P1PRIORITY", "summary": "P1", "type": "priority_reference" }, "service": { "html_url": "https://example.pagerduty.com/services/PX123456", "id": "PX123456", "summary": "Production API", "type": "service_reference" }, "status": "triggered", "title": "Server is on fire", "updated_at": "2024-01-15T12:00:00Z", "urgency": "high" }, { "acknowledgements": [ { "acknowledger": { "html_url": "https://example.pagerduty.com/users/PUSER01", "id": "PUSER01", "summary": "John Doe", "type": "user_reference" }, "at": "2024-01-15T12:35:00Z" } ], "assignments": [ { "assignee": { "html_url": "https://example.pagerduty.com/users/PUSER01", "id": "PUSER01", "summary": "John Doe", "type": "user_reference" }, "at": "2024-01-15T12:30:00Z" } ], "created_at": "2024-01-15T12:30:00Z", "description": "Database connections are timing out", "escalation_policy": { "html_url": "https://example.pagerduty.com/escalation_policies/PABCDEF", "id": "PABCDEF", "summary": "Default Escalation Policy", "type": "escalation_policy_reference" }, "html_url": "https://example.pagerduty.com/incidents/PT4KHLM", "id": "PT4KHLM", "incident_number": 1235, "priority": { "id": "P2PRIORITY", "summary": "P2", "type": "priority_reference" }, "service": { "html_url": "https://example.pagerduty.com/services/PX123456", "id": "PX123456", "summary": "Production API", "type": "service_reference" }, "status": "acknowledged", "title": "Database connection issues", "updated_at": "2024-01-15T12:35:00Z", "urgency": "high" } ], "total": 2 }, "timestamp": "2024-01-15T13:00:00Z", "type": "pagerduty.incidents.list"}List Log Entries
Section titled “List Log Entries”The List Log Entries component retrieves all log entries (audit trail) for a PagerDuty incident.
Use Cases
Section titled “Use Cases”- Audit trail: Access complete incident history for compliance or review
- Timeline reconstruction: Build a detailed timeline of all incident activity
- Incident analysis: Analyze escalation patterns and response times
- Forensics: Review all actions taken during an incident
Configuration
Section titled “Configuration”- Incident ID: The ID of the incident to list log entries for (e.g., A12BC34567…)
- Limit: Maximum number of log entries to return (default: 100)
Output
Section titled “Output”Returns a list of log entries with:
- id: Log entry ID
- type: The type of log entry (e.g., trigger_log_entry, acknowledge_log_entry, annotate_log_entry)
- summary: A summary of what happened
- created_at: When the log entry was created
- agent: The agent (user or service) that caused the log entry
- channel: The channel through which the action was performed
Example Output
Section titled “Example Output”{ "data": { "log_entries": [ { "agent": { "html_url": "https://acme.pagerduty.com/services/PLH1HKV", "id": "PLH1HKV", "summary": "API Service", "type": "service_reference" }, "channel": { "type": "api" }, "created_at": "2024-01-15T10:00:00Z", "id": "Q02JTSNZWHSEKV", "summary": "Triggered through the API", "type": "trigger_log_entry" }, { "agent": { "html_url": "https://acme.pagerduty.com/users/PUSER01", "id": "PUSER01", "summary": "John Smith", "type": "user_reference" }, "channel": { "type": "web_ui" }, "created_at": "2024-01-15T10:15:00Z", "id": "Q02JTSNZWHSEKW", "summary": "Acknowledged by John Smith", "type": "acknowledge_log_entry" }, { "agent": { "html_url": "https://acme.pagerduty.com/users/PUSER01", "id": "PUSER01", "summary": "John Smith", "type": "user_reference" }, "channel": { "type": "web_ui" }, "created_at": "2024-01-15T10:30:00Z", "id": "Q02JTSNZWHSEKX", "summary": "John Smith added a note", "type": "annotate_log_entry" } ], "total": 3 }, "timestamp": "2024-01-15T11:00:00Z", "type": "pagerduty.log_entries.list"}List Notes
Section titled “List Notes”The List Notes component retrieves all notes (timeline entries) for a PagerDuty incident.
Use Cases
Section titled “Use Cases”- Incident review: Review all notes added to an incident
- Timeline reconstruction: Build a timeline of incident updates
- Audit trail: Access the history of notes for compliance or review
- Note analysis: Process or analyze notes for patterns or keywords
Configuration
Section titled “Configuration”- Incident ID: The ID of the incident to list notes for (e.g., A12BC34567…)
Output
Section titled “Output”Returns a list of notes with:
- id: Note ID
- content: The note content
- created_at: When the note was created
- user: The user who created the note
- channel: The channel through which the note was created
Example Output
Section titled “Example Output”{ "data": { "notes": [ { "channel": { "type": "web_ui" }, "content": "Investigation started. Checking server logs for anomalies.", "created_at": "2024-01-15T10:30:00Z", "id": "PVL9NF8", "user": { "html_url": "https://acme.pagerduty.com/users/PLH1HKV", "id": "PLH1HKV", "summary": "John Smith", "type": "user_reference" } }, { "channel": { "type": "web_ui" }, "content": "Root cause identified: memory leak in the cache service. Deploying fix now.", "created_at": "2024-01-15T10:45:00Z", "id": "PVL9NF9", "user": { "html_url": "https://acme.pagerduty.com/users/PLH1HKV", "id": "PLH1HKV", "summary": "John Smith", "type": "user_reference" } }, { "channel": { "type": "api" }, "content": "Fix deployed successfully. Monitoring for stability.", "created_at": "2024-01-15T11:00:00Z", "id": "PVL9NFA", "user": { "html_url": "https://acme.pagerduty.com/users/PLH1HKW", "id": "PLH1HKW", "summary": "Jane Doe", "type": "user_reference" } } ], "total": 3 }, "timestamp": "2024-01-15T11:05:00Z", "type": "pagerduty.notes.list"}Resolve Incident
Section titled “Resolve Incident”The Resolve Incident component resolves an existing PagerDuty incident.
Use Cases
Section titled “Use Cases”- Incident closure: Resolve an incident when the issue has been fixed
- Automated resolution: Automatically resolve incidents based on recovery signals
- Integration workflows: Resolve incidents when related events occur in other systems
Configuration
Section titled “Configuration”- Incident ID: The ID of the incident to resolve (e.g., A12BC34567…)
- From Email: Email address of a valid PagerDuty user (required for App OAuth, optional for API tokens)
- Resolution Notes: Optional notes about the resolution (saved to incident description)
Behavior
Section titled “Behavior”When an incident is resolved, the incident status changes to “resolved” and all escalations stop. If resolution notes are provided, they will be saved to the incident description.
Output
Section titled “Output”Returns the resolved incident object with all current information.
Example Output
Section titled “Example Output”{ "data": { "incident": { "assigned_via": "escalation_policy", "assignments": [], "created_at": "2015-10-06T21:30:42Z", "escalation_policy": { "html_url": "https://subdomain.pagerduty.com/escalation_policies/PT20YPA", "id": "PT20YPA", "self": "https://api.pagerduty.com/escalation_policies/PT20YPA", "summary": "Another Escalation Policy", "type": "escalation_policy_reference" }, "first_trigger_log_entry": { "html_url": "https://subdomain.pagerduty.com/incidents/PT4KHLK/log_entries/Q02JTSNZWHSEKV", "id": "Q02JTSNZWHSEKV", "self": "https://api.pagerduty.com/log_entries/Q02JTSNZWHSEKV?incident_id=PT4KHLK", "summary": "Triggered through the API", "type": "trigger_log_entry_reference" }, "html_url": "https://subdomain.pagerduty.com/incidents/PT4KHLK", "id": "PT4KHLK", "incident_key": "baf7cf21b1da41b4b0221008339ff357", "incident_number": 1234, "last_status_change_at": "2015-10-06T21:45:00Z", "last_status_change_by": { "html_url": "https://subdomain.pagerduty.com/users/PXPGF42", "id": "PXPGF42", "self": "https://api.pagerduty.com/users/PXPGF42", "summary": "Earline Greenholt", "type": "user_reference" }, "priority": { "id": "P53ZZH5", "self": "https://api.pagerduty.com/priorities/P53ZZH5", "summary": "P2", "type": "priority_reference" }, "resolved_at": "2015-10-06T21:45:00Z", "self": "https://api.pagerduty.com/incidents/PT4KHLK", "service": { "html_url": "https://subdomain.pagerduty.com/service-directory/PWIXJZS", "id": "PWIXJZS", "self": "https://api.pagerduty.com/services/PWIXJZS", "summary": "My Mail Service", "type": "service_reference" }, "status": "resolved", "summary": "[#1234] The server is on fire.", "teams": [ { "html_url": "https://subdomain.pagerduty.com/teams/PQ9K7I8", "id": "PQ9K7I8", "self": "https://api.pagerduty.com/teams/PQ9K7I8", "summary": "Engineering", "type": "team_reference" } ], "title": "The server is on fire.", "type": "incident", "updated_at": "2015-10-06T21:45:00Z", "urgency": "high" } }, "timestamp": "2026-01-19T12:00:00Z", "type": "pagerduty.incident"}Snooze Incident
Section titled “Snooze Incident”The Snooze Incident component temporarily pauses notifications for an acknowledged PagerDuty incident.
Use Cases
Section titled “Use Cases”- Temporary acknowledgement: Snooze an incident while investigating
- Scheduled follow-up: Re-trigger the incident after a specified time
- Avoid escalation: Prevent escalation while work is in progress
Configuration
Section titled “Configuration”- Incident ID: The ID of the incident to snooze (must be in acknowledged state)
- Duration: How long to snooze the incident (1 hour, 4 hours, 8 hours, or 24 hours)
- From Email: Email address of a valid PagerDuty user (required for App OAuth, optional for API tokens)
Behavior
Section titled “Behavior”When an incident is snoozed, it will remain in the acknowledged state and no further notifications will be sent. After the snooze duration expires, the incident will return to a triggered state and notifications will resume.
Note: Reassigning a snoozed incident will cancel the snooze timer.
Output
Section titled “Output”Returns the snoozed incident object with all current information.
Example Output
Section titled “Example Output”{ "data": { "incident": { "assigned_via": "escalation_policy", "assignments": [ { "assignee": { "html_url": "https://subdomain.pagerduty.com/users/PXPGF42", "id": "PXPGF42", "self": "https://api.pagerduty.com/users/PXPGF42", "summary": "Earline Greenholt", "type": "user_reference" }, "at": "2015-11-10T00:31:52Z" } ], "created_at": "2015-10-06T21:30:42Z", "escalation_policy": { "html_url": "https://subdomain.pagerduty.com/escalation_policies/PT20YPA", "id": "PT20YPA", "self": "https://api.pagerduty.com/escalation_policies/PT20YPA", "summary": "Another Escalation Policy", "type": "escalation_policy_reference" }, "first_trigger_log_entry": { "html_url": "https://subdomain.pagerduty.com/incidents/PT4KHLK/log_entries/Q02JTSNZWHSEKV", "id": "Q02JTSNZWHSEKV", "self": "https://api.pagerduty.com/log_entries/Q02JTSNZWHSEKV?incident_id=PT4KHLK", "summary": "Triggered through the API", "type": "trigger_log_entry_reference" }, "html_url": "https://subdomain.pagerduty.com/incidents/PT4KHLK", "id": "PT4KHLK", "incident_key": "baf7cf21b1da41b4b0221008339ff357", "incident_number": 1234, "last_status_change_at": "2015-10-06T21:38:23Z", "last_status_change_by": { "html_url": "https://subdomain.pagerduty.com/users/PXPGF42", "id": "PXPGF42", "self": "https://api.pagerduty.com/users/PXPGF42", "summary": "Earline Greenholt", "type": "user_reference" }, "priority": { "id": "P53ZZH5", "self": "https://api.pagerduty.com/priorities/P53ZZH5", "summary": "P2", "type": "priority_reference" }, "resolved_at": null, "self": "https://api.pagerduty.com/incidents/PT4KHLK", "service": { "html_url": "https://subdomain.pagerduty.com/service-directory/PWIXJZS", "id": "PWIXJZS", "self": "https://api.pagerduty.com/services/PWIXJZS", "summary": "My Mail Service", "type": "service_reference" }, "status": "acknowledged", "summary": "[#1234] The server is on fire.", "teams": [ { "html_url": "https://subdomain.pagerduty.com/teams/PQ9K7I8", "id": "PQ9K7I8", "self": "https://api.pagerduty.com/teams/PQ9K7I8", "summary": "Engineering", "type": "team_reference" } ], "title": "The server is on fire.", "type": "incident", "updated_at": "2015-10-06T21:40:23Z", "urgency": "high" } }, "timestamp": "2026-01-19T12:00:00Z", "type": "pagerduty.incident"}Update Incident
Section titled “Update Incident”The Update Incident component modifies an existing PagerDuty incident.
Use Cases
Section titled “Use Cases”- Status updates: Update incident status (acknowledge, resolve)
- Priority management: Change incident priority
- Assignment: Assign incidents to users or escalation policies
Configuration
Section titled “Configuration”- Incident ID: The ID of the incident to update (e.g., A12BC34567…)
- From Email: Email address of a valid PagerDuty user (required for App OAuth, optional for API tokens)
- Status: Update incident status (acknowledged, resolved)
- Priority: Update incident priority (select from available priorities)
- Title: Update incident title (optional, supports expressions)
- Description: Update incident description (optional, supports expressions)
- Escalation Policy: Change escalation policy (optional)
- Assignees: Assign to specific users (optional)
Output
Section titled “Output”Returns the updated incident object with all current information.
Example Output
Section titled “Example Output”{ "data": { "incident": { "assigned_via": "escalation_policy", "assignments": [ { "assignee": { "html_url": "https://subdomain.pagerduty.com/users/PXPGF42", "id": "PXPGF42", "self": "https://api.pagerduty.com/users/PXPGF42", "summary": "Earline Greenholt", "type": "user_reference" }, "at": "2015-11-10T00:31:52Z" } ], "created_at": "2015-10-06T21:30:42Z", "escalation_policy": { "html_url": "https://subdomain.pagerduty.com/escalation_policies/PT20YPA", "id": "PT20YPA", "self": "https://api.pagerduty.com/escalation_policies/PT20YPA", "summary": "Another Escalation Policy", "type": "escalation_policy_reference" }, "first_trigger_log_entry": { "html_url": "https://subdomain.pagerduty.com/incidents/PT4KHLK/log_entries/Q02JTSNZWHSEKV", "id": "Q02JTSNZWHSEKV", "self": "https://api.pagerduty.com/log_entries/Q02JTSNZWHSEKV?incident_id=PT4KHLK", "summary": "Triggered through the API", "type": "trigger_log_entry_reference" }, "html_url": "https://subdomain.pagerduty.com/incidents/PT4KHLK", "id": "PT4KHLK", "incident_key": "baf7cf21b1da41b4b0221008339ff357", "incident_number": 1234, "incident_type": { "name": "major_incident" }, "last_status_change_at": "2015-10-06T21:38:23Z", "last_status_change_by": { "html_url": "https://subdomain.pagerduty.com/users/PXPGF42", "id": "PXPGF42", "self": "https://api.pagerduty.com/users/PXPGF42", "summary": "Earline Greenholt", "type": "user_reference" }, "priority": { "id": "P53ZZH5", "self": "https://api.pagerduty.com/priorities/P53ZZH5", "summary": "P2", "type": "priority_reference" }, "resolved_at": null, "self": "https://api.pagerduty.com/incidents/PT4KHLK", "service": { "html_url": "https://subdomain.pagerduty.com/service-directory/PWIXJZS", "id": "PWIXJZS", "self": "https://api.pagerduty.com/services/PWIXJZS", "summary": "My Mail Service", "type": "service_reference" }, "status": "acknowledged", "summary": "[#1234] The server is on fire.", "teams": [ { "html_url": "https://subdomain.pagerduty.com/teams/PQ9K7I8", "id": "PQ9K7I8", "self": "https://api.pagerduty.com/teams/PQ9K7I8", "summary": "Engineering", "type": "team_reference" } ], "title": "The server is on fire.", "type": "incident", "updated_at": "2015-10-06T21:40:23Z", "urgency": "high" } }, "timestamp": "2026-01-19T12:00:00Z", "type": "pagerduty.incident"}