ActionPagerDutyUpdated September 2026

How do I resolve a PagerDuty incident?

Short answer: You can resolve pagerduty incident in PagerDuty by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the PagerDuty Resolve PagerDuty Incident action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Resolve PagerDuty Incident in PagerDuty — start free All 5 PagerDuty actions

Resolve PagerDuty Incident in PagerDuty — start free

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.

Triggered by

Apps that pair well as the trigger for Resolve PagerDuty Incident.

Any of these apps can fire this action as part of a workflow.

Google Sheets → PagerDuty

2 Google Sheets triggers

HubSpot → PagerDuty

18 HubSpot triggers

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 run history shows the failed step with its input and the error message PagerDuty returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Resolve PagerDuty Incident support batch operations?

Run Resolve PagerDuty Incident inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within PagerDuty's rate limits.

More actions