> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ravenna.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# PagerDuty workflow actions

> Use PagerDuty workflow actions in Ravenna to validate on-call status, retrieve current responders, and route incidents to active engineers.

Use PagerDuty actions in workflows to validate on-call membership and make routing decisions based on on-call schedules.

## Actions

<AccordionGroup>
  <Accordion title="Validate On-Call Membership">
    Validates if a user is currently on-call in PagerDuty. Use this to verify on-call status before escalating tickets, route incidents to the right responders, or make conditional decisions based on on-call schedules.

    **Common use cases:**

    * Verify on-call status before escalation
    * Route incidents to on-call responders
    * Check escalation eligibility
    * Validate incident assignments based on schedules

    **Configuration:**

    * **User**: The user to check on-call status for.
    * **Schedules**: One or more PagerDuty schedules to check. The action returns success if the user is on-call for any of the selected schedules. Leave empty to check across all schedules in your PagerDuty account.

    You can find a schedule ID in the URL when viewing the schedule in PagerDuty (`https://your-subdomain.pagerduty.com/schedules#<schedule_id>`).
  </Accordion>

  <Accordion title="Get On-Call Users">
    Retrieves users currently on-call in PagerDuty and matches them to Ravenna users by email. Returns the list of matched Ravenna user IDs so downstream steps can assign, notify, or route based on the active rotation.

    Optionally scope the lookup to one or more PagerDuty schedules, or provide a time range to check who is on-call during a specific window. If no schedules are specified, all schedules are checked. If no time range is provided, the action returns users on-call right now.

    **Common use cases:**

    * Auto-assign incoming tickets to whoever is currently on-call
    * Notify on-call engineers when a high-priority ticket arrives
    * Build routing rules that dynamically target the active on-call rotation
    * Populate ticket fields with on-call responder information
  </Accordion>
</AccordionGroup>