PagerDuty

Add PagerDuty actions to your InvGate Service Management workflows

The PagerDuty built-in action connector reads live alerting data as a workflow step: who is on call right now, which schedules and escalation policies apply, and the current state of incidents, services, and users. A process can query that data and route on it.

Why you should connect PagerDuty to your workflows

Assignment rules built on a static list of names go wrong the moment the rota changes. Reading the on-call schedule at run time means the workflow routes to whoever is actually covering the shift, and can check the matching escalation policy before it decides. During a major incident, the same data tells the process which service is affected and who already owns it.

Benefits of integrating InvGate Service Management with PagerDuty

PagerDuty actions live in the Integrations section of the workflow editor and are available on Pro plans and above. All currently available actions are read-only, so the connector cannot alter your PagerDuty configuration.

Routing that tracks the rota

The workflow reads the live on-call shift, so work reaches the person covering it instead of a name hard-coded into a rule.

Escalation context before escalating

A process can check the relevant escalation policy and service ownership first, so major incidents follow the path your alerting already defines.

Read-only

Every available action is a retrieval. The connector consumes your PagerDuty data without changing incidents or schedules.