Acknowledge / Resolve
pagerduty.set_incident_status
ActionBusiness appsconnection required
Calls the PagerDuty API with the connection's credentials.
Set an incident's status.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- PagerDuty
- Secret shape
- the REST API token, or {"token": "…"}
- Config it needs
- from_email
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
incident_id Id of the incident to act on, from pagerduty.list_incidents — not its name. | string | Yes | — | — | — |
status acknowledged or resolved. | string | Yes | — | — | — |
Output
One shape.
result
The provider's response object, as returned.
Extra keys beyond the ones listed can appear.
{}Related PagerDuty nodes
Solutions with PagerDuty
See Acknowledge / Resolve run in a workflow.
In a technical demo we add the PagerDuty connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.