Start free
ActionStatuspageUpdated June 2026

What Statuspage components exist?

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

List Statuspage Components in Statuspage — start free All 4 Statuspage actions
List Statuspage Components in Statuspage — start free
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.

Gmail → Statuspage
1 Gmail triggers
Slack → Statuspage
13 Slack triggers
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. TinyCommand handles Statuspage's rate limits automatically so you don't have to throttle manually.
More actions

Other Statuspage actions.

Action
Create Statuspage Incident
Opens an incident with status, affected components, body. For "monitoring detected outage → auto-post to status page" workflows that keep customers informed.
Action
Update Statuspage Component
Transitions a component (operational, degraded_performance, partial_outage, major_outage). For "monitor signals degradation → reflect on status page" or for "incident resolved → set back to operational" workflows.
Action
Update Statuspage Incident
Adds an update post to an existing incident. For "investigating → identified → monitoring → resolved" lifecycle updates posted automatically.
List Statuspage Components in Statuspage — start free