ActionStatuspageUpdated May 2026

What Statuspage components exist?

Short answer: Drop the "Statuspage → List Statuspage Components" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 4 Statuspage actions

Sample request

{}

Returns

[
  {
    "id": "comp_abc",
    "name": "API",
    "status": "operational"
  }
]

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

Triggered by

Apps that pair well as the trigger for List Statuspage Components.

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

Google Sheets → Statuspage

2 Google Sheets triggers

HubSpot → Statuspage

18 HubSpot triggers

FAQ

Questions about List Statuspage Components.

What does the List Statuspage Components action do in Statuspage?

Returns the configured system components (API, Database, Web App, etc.) with current status. Useful for resolving component IDs at workflow setup.

What inputs does List Statuspage Components require?

List Statuspage Components 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 Statuspage 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 Statuspage Components support batch operations?

Yes. Run List Statuspage Components inside a Loop node to process arrays. Tiny Command handles Statuspage's rate limits automatically so you don't have to throttle manually.

More actions