Start free
ActionPagerDutyUpdated June 2026

How do I acknowledge a PagerDuty incident?

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

Acknowledge PagerDuty Incident in PagerDuty — start free All 5 PagerDuty actions
Acknowledge 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.

FieldTypeRequiredDescription
Incident ID
incident_id
stringRequiredIncident ID. Example: PT4KHLK
Sample request
{
  "incident_id": "e.g. PT4KHLK"
}
Returns
{
  "incident": {
    "id": "PT4KHLK",
    "status": "acknowledged"
  }
}

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

Triggered by

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

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

Gmail → PagerDuty
1 Gmail triggers
Slack → PagerDuty
13 Slack triggers
Google Sheets → PagerDuty
2 Google Sheets triggers
HubSpot → PagerDuty
18 HubSpot triggers
FAQ

Questions about Acknowledge PagerDuty Incident.

What does the Acknowledge PagerDuty Incident action do in PagerDuty?
Marks an incident as acknowledged — stops escalation but keeps it open. For "Slack reaction roller → ack the incident" workflows that integrate chat-based acknowledgement.
What inputs does Acknowledge 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 Acknowledge PagerDuty Incident support batch operations?
Yes. Run Acknowledge PagerDuty Incident inside a Loop node to process arrays. TinyCommand handles PagerDuty's rate limits automatically so you don't have to throttle manually.
More actions

Other PagerDuty actions.

Action
Create PagerDuty Incident
Opens an incident with title, service, urgency, dedup_key for fan-in. The standard hook for "external monitor detected → page the on-call engineer" workflows.
Action
List PagerDuty Incidents
Paginated incidents with filters by service, status, urgency. For "current active incidents" dashboards and post-incident reporting workflows.
Action
List PagerDuty Services
Returns the service catalog. Useful for resolving service IDs at workflow setup and for inventorying alert-routing structure.
Action
Resolve PagerDuty Incident
Closes an incident. For "monitoring source signals recovery → auto-resolve" or for self-healing systems that emit recovery events.
Acknowledge PagerDuty Incident in PagerDuty — start free