Resolve PagerDuty Incident: PagerDuty action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Incident ID incidentId	string	Required	Incident ID
Resolution Notes resolution	string	Optional	Resolution Notes

Sample request

{
  "incidentId": "{{trigger.incidentId}}",
  "resolution": "{{trigger.resolution}}"
}

Returns

{
  "incident": {
    "id": "P123ABC",
    "status": "resolved",
    "resolved_at": "2026-04-11T12:00:00Z"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Resolve PagerDuty Incident.

What does the Resolve PagerDuty Incident action do in PagerDuty?

Closes an incident. For "monitoring source signals recovery → auto-resolve" or for self-healing systems that emit recovery events.

What inputs does Resolve PagerDuty Incident require?

Required: Incident ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if PagerDuty returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Resolve PagerDuty Incident support batch operations?

Yes. Run Resolve PagerDuty Incident inside a Loop node to process arrays. Tiny Command handles PagerDuty's rate limits automatically so you don't have to throttle manually.

More actions