PagerDuty

Stop guessing who's on call

Checking on-call status used to mean leaving your ticket, logging into PagerDuty, and coming back to update it. With native PagerDuty actions in Workflow Builder, that lookup happens inside the automation, so tickets route to the right engineer without anyone leaving InvGate.

Nine actions, one workflow builder

All PagerDuty actions are read-only, so they're safe to drop into any workflow without risking changes in PagerDuty itself. Add them from Workflows > Workflow Builder > Add Action > PagerDuty.

List Incidents: Pull every open incident for a service or the full account.
Get Incident: Retrieve full detail on a single incident.
List Services: See every service configured in PagerDuty.
Get Service: Check the status and detail of one service.
List Users: Query the full PagerDuty user directory.
Get User: Retrieve one user's contact and role information.
List On-Calls: Find out who's on call right now, for any schedule.
List Schedules: Pull all configured on-call schedules.
List Escalation Policies: Retrieve the escalation path tied to a service.

Example: auto-triage a service impact request

Combine PagerDuty actions with Confluence to build a workflow that checks for active incidents and pulls the right runbook automatically, no manual triage required.

• A user reports impact on a service through a request form.
• The workflow runs Get Service to identify the affected service in PagerDuty.
• List Incidents checks whether that service has an active incident.
• If it does, priority is set to high and the on-call team is notified.
• If it doesn't, priority is set to medium.
• A Confluence action retrieves the runbook URL, and the workflow executes it automatically.

Built for incident-heavy IT teams

Faster triage: Tickets get the right priority automatically, based on live incident status.
Route to the right engineer: On-call data flows straight into ticket assignment, no manual checks.
No manual lookups: Skip the tab-switching between InvGate and PagerDuty.
Safe at scale: Read-only actions can be reused across as many workflows as you need.