ActionPagerDutyUpdated September 2026

What PagerDuty services are configured?

Short answer: You can list pagerduty services in PagerDuty by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the PagerDuty List PagerDuty Services 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.

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

List PagerDuty Services 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
Limit limit	string	Optional	Limit. e.g. "25"
Search Query query	string	Optional	Search Query. Example: API

Sample request

{
  "limit": "25",
  "query": "e.g. API"
}

Returns

{
  "services": [
    {
      "id": "PABC123",
      "name": "API Service",
      "status": "active",
      "escalation_policy": {
        "id": "PDEF456"
      }
    }
  ]
}

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

Triggered by

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

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 Services.

What does the List PagerDuty Services action do in PagerDuty?

Returns the service catalog. Useful for resolving service IDs at workflow setup and for inventorying alert-routing structure.

What inputs does List PagerDuty Services require?

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

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