ActionStatuspageUpdated September 2026
How do I change a Statuspage component status?
Short answer: You can update statuspage component in Statuspage by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Statuspage Update Statuspage Component 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.
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 |
|---|---|---|---|
Component ID component_id | string | Required | The Component ID assigned by Statuspage. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Status status | options | Required | – |
Sample request
{"component_id": "{{trigger.component_id}}","status": "{{trigger.status}}"}
Returns
{"id": "comp_abc","name": "API","status": "degraded_performance"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Update Statuspage Component.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Update Statuspage Component.
What does the Update Statuspage Component action do in Statuspage?
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.
What inputs does Update Statuspage Component require?
Required: Component ID, Status. Every input accepts a static value or a variable from any upstream node in your workflow.
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 Update Statuspage Component support batch operations?
Run Update Statuspage Component 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.
ActionList Statuspage Components
Returns the configured system components (API, Database, Web App, etc.) with current status. Useful for resolving component IDs at workflow setup.
ActionUpdate Statuspage Incident
Adds an update post to an existing incident. For "investigating → identified → monitoring → resolved" lifecycle updates posted automatically.