ActionPagerDutyUpdated September 2026

How do I list PagerDuty incidents?

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

List PagerDuty Incidents in PagerDuty — start free All 5 PagerDuty actions

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.

Triggered by

Apps that pair well as the trigger for List PagerDuty Incidents.

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

Run List PagerDuty Incidents 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