How to list pagerduty incidents in PagerDuty

List PagerDuty Incidents 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
Status statuses[]	options	Optional	Status. Options: Triggered, Acknowledged, Resolved
Limit limit	string	Optional	Limit. e.g. "25"
Sort By sort_by	options	Optional	Sort By. Options: Newest first, Oldest first

Sample request

{
  "statuses[]": "{{trigger.statuses[]}}",
  "limit": "25",
  "sort_by": "{{trigger.sort_by}}"
}

Returns

{
  "incidents": [
    {
      "id": "PT4KHLK",
      "title": "API down",
      "status": "triggered",
      "urgency": "high",
      "incident_number": 1234
    }
  ]
}

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

FAQ

Questions about List PagerDuty Incidents.

What does the List PagerDuty Incidents action do in PagerDuty?

Paginated incidents with filters by service, status, urgency. For "current active incidents" dashboards and post-incident reporting workflows.

What inputs does List PagerDuty Incidents require?

List PagerDuty Incidents has no required inputs. Sensible defaults are applied if you leave fields blank.

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 List PagerDuty Incidents support batch operations?

Yes. Run List PagerDuty Incidents inside a Loop node to process arrays. TinyCommand handles PagerDuty's rate limits automatically so you don't have to throttle manually.

More actions