Use PagerDuty with Automation

Use PagerDuty actions in Jira Automation to create and manage incidents, pull incident and service details, view alerts, sync notes, and find who’s on call. Choose an action below and enter the fields shown (or use smart values) to build your rule.


Create incident in PagerDuty

You can use this action to create an incident in PagerDuty for a specific service. This helps you quickly raise and track issues directly from your automation rules.

Enter the following fields or select using smart values:

  • Incident title: Enter a short summary that clearly describes the problem. This title appears in notifications and incident lists, so make it easy to scan.

  • Service ID: Enter the PagerDuty service ID where you want to create the incident. This controls which escalation policy and integrations are used.

  • Urgency: Select the urgency level for the incident. Use high for critical issues that need immediate attention, or low for less urgent problems.

  • Incident type: Enter the incident type, such as disruption or maintenance, to categorize the nature of the incident.


List incidents from PagerDuty

You can use this action to list incidents from PagerDuty with optional filters. This is useful for building dashboards or syncing incident status into Jira.

Enter the following fields or select using smart values:

  • Limit: Enter the maximum number of incidents to return in one request, up to 100.

  • Offset: Enter the starting index for results to support pagination. Use 0 for the first page.

  • Total: Select whether to include the total number of matching incidents in the response.

  • Objects to include: Enter related objects to include, such as users, services, or escalation_policies, as a comma‑separated list.

  • Status: Enter incident statuses to filter by, such as triggered, acknowledged, or resolved, as a comma‑separated list.

  • Urgencies: Enter urgency levels to filter by, such as high or low, as a comma‑separated list.


Get incident from PagerDuty

You can use this action to get full details for a specific PagerDuty incident. This helps you show incident context or check the latest status before updating it.

Enter the following fields or select using smart values:

  • Incident ID: Enter the PagerDuty incident ID you want to retrieve.

  • Objects to include: Enter related objects to include, such as acknowledgers, assignees, or priorities, as a comma‑separated list.


Update incident in PagerDuty

You can use this action to update the status or properties of an existing PagerDuty incident. This helps you acknowledge, resolve, or reassign incidents directly from Jira.

Enter the following fields or select using smart values:

  • Incident ID: Enter the PagerDuty incident ID you want to update.

  • Email: Enter the email address of the PagerDuty user making this change. This must match a valid user in PagerDuty.

  • Incident type: Select the incident resource type to update, such as incident or incident_reference.

  • Status: Select the new status for the incident, such as acknowledged or resolved.

  • Priority ID: Enter the PagerDuty priority ID to assign to this incident, such as a defined P1 or P2.

  • Incident title: Enter the updated title or summary for the incident.

  • Urgency: Select the new urgency level for the incident, such as high or low.

  • Service ID: Enter the PagerDuty service ID to move this incident to if you want to change the service.


List incident alerts in PagerDuty

You can use this action to list alerts associated with a specific PagerDuty incident. This helps you review the monitoring events that triggered or updated the incident.

Enter the following fields or select using smart values:

  • Incident ID: Enter the PagerDuty incident ID for which you want to list the alerts.

  • Limit: Enter the maximum number of alerts to return in one request.

  • Offset: Enter the starting index for alert results to support pagination.

  • Total: Select whether to include the total number of matching alerts in the response.

  • Objects to include: Enter related objects to include, such as services or incidents, as a comma‑separated list.

  • Sort by: Select how to sort alerts, such as created_at:asc or created_at:desc.

  • Status: Enter alert statuses to filter by, such as triggered, acknowledged, or resolved, as a comma‑separated list.

  • Alert key: Enter a specific alert deduplication key to filter alerts from a particular monitoring source.


Get on-call users in PagerDuty

You can use this action to get a list of users who are currently on call in PagerDuty. This helps you route Jira issues or notifications to the right responder.

Enter the following fields or select using smart values:

  • Limit: Enter the maximum number of on‑call entries to return in one request.

  • Offset: Enter the starting index for on‑call results to support pagination.

  • Total: Select whether to include the total number of matching on‑call entries in the response.

  • Earliest only: Select whether to return only the user at the earliest escalation level currently on call.

  • Since: Enter the start of the time range to check on‑call coverage, in ISO 8601 format.

  • Objects to include: Enter related objects to include, such as users, schedules, or escalation_policies, as a comma‑separated list.


List services in PagerDuty

You can use this action to list services from PagerDuty with optional filters. This is useful for populating dropdowns or mapping Jira projects to PagerDuty services.

Enter the following fields or select using smart values:

  • Limit: Enter the maximum number of services to return in one request.

  • Offset: Enter the starting index for service results to support pagination.

  • Query: Enter a search term to filter services by name or description.

  • Total: Select whether to include the total number of matching services in the response.

  • Objects to include: Enter related objects to include, such as escalation_policies or teams, as a comma‑separated list.

  • Name: Enter the exact service name to filter by.

  • Sort by: Select how to sort services, such as name:asc or name:desc.


Get service from PagerDuty

You can use this action to get full details for a specific PagerDuty service. This helps you show escalation policies and integrations alongside Jira issues.

Enter the following fields or select using smart values:

  • Service ID: Enter the PagerDuty service ID you want to retrieve.

  • Objects to include: Enter related objects to include, such as escalation_policies, teams, or integrations, as a comma‑separated list.


List incident notes in PagerDuty

You can use this action to list notes added to a specific PagerDuty incident. This helps you sync responder commentary into Jira for a complete incident history.

Enter the following fields or select using smart values:

  • Incident ID: Enter the PagerDuty incident ID whose notes you want to list.


List incident log entries in PagerDuty

You can use this action to list log entries for a specific PagerDuty incident. This helps you build a detailed incident timeline in Jira.

Enter the following fields or select using smart values:

  • Incident ID: Enter the PagerDuty incident ID whose log entries you want to list.

  • Limit: Enter the maximum number of log entries to return in one request.

  • Offset: Enter the starting index for log entry results to support pagination.

  • Total: Select whether to include the total number of matching log entries in the response.

  • Overview only: Select whether to return only a summary view of each log entry.

  • Objects to include: Enter related objects to include, such as incidents, services, channels, or teams, as a comma‑separated list.

  • Since: Enter the start of the time range to filter log entries, in ISO 8601 format.

  • Until: Enter the end of the time range to filter log entries, in ISO 8601 format.


Add note to PagerDuty incident

You can use this action to add a note to a specific PagerDuty incident. This helps you sync Jira comments or updates into PagerDuty during incident response.

Enter the following fields or select using smart values:

  • Incident ID: Enter the PagerDuty incident ID you want to add the note to.

  • From email: Enter the email address of the PagerDuty user adding this note. This must match a valid user in PagerDuty.

  • Note content: Enter the text content of the note you want to add to the incident.


Snooze incident in PagerDuty

You can use this action to snooze a PagerDuty incident for a set duration. This helps you pause notifications for non‑critical incidents until a later time.

Enter the following fields or select using smart values:

  • Incident ID: Enter the PagerDuty incident ID you want to snooze.

  • From email: Enter the email address of the PagerDuty user performing the snooze. This must match a valid user in PagerDuty.

  • Duration (seconds): Enter how long to snooze the incident for, in seconds.

Still need help?

The Atlassian Community is here for you.