ActionStatuspageUpdated September 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.
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.
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 run history shows the failed step with its input and the error message Statuspage 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 Statuspage Components support batch operations?
Run List Statuspage Components 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 Statuspage's rate limits.
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.
ActionUpdate 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.
ActionUpdate Statuspage Incident
Adds an update post to an existing incident. For "investigating → identified → monitoring → resolved" lifecycle updates posted automatically.