Incident management workflows for PagerDuty REST API v2.
PagerDuty currently provides 3 triggers that can start a workflow and 6 actions a workflow can run. Use those building blocks to connect product and engineering activity to the customers and work it affects.
New Incident
Triggers when a new incident is created
Incident Resolved
Triggers when an incident is resolved.
Incident Acknowledged
Triggers when an incident is acknowledged.
Create Incident
Create a new PagerDuty incident using the REST API.
List Incidents
List PagerDuty incidents with optional filters and pagination.
Get Incident
Retrieve a PagerDuty incident by ID.
Acknowledge Incident
Acknowledge an existing PagerDuty incident.
Resolve Incident
Resolve an existing PagerDuty incident.
Custom API Call
Make a custom API call to PagerDuty REST API v2. Authorization, Accept, and Content-Type headers are injected automatically. For write endpoints that require a From header, add it manually in the headers field.
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported PagerDuty event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Incident
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported PagerDuty action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Incident
Combine PagerDuty with another integration and Coherence records to connect product and engineering activity to the customers and work it affects.
Starts with
New Incident
Finishes with
Create Incident, then preserve the outcome in Coherence
The exact authentication fields depend on PagerDuty. The workflow structure stays straightforward:
Authorize the PagerDuty account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with PagerDuty or provide a complementary trigger or action.
PagerDuty currently provides 3 triggers that can start a workflow and 6 actions a workflow can run. Use those building blocks to connect product and engineering activity to the customers and work it affects.
PagerDuty currently lists 3 triggers and 6 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported PagerDuty triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
