Start free
ActionStatuspageUpdated June 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.

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

FieldTypeRequiredDescription
Component ID
component_id
stringRequiredThe 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
optionsRequired–
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.

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 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 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 Update Statuspage Component support batch operations?
Yes. Run Update Statuspage Component 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
List Statuspage Components
Returns the configured system components (API, Database, Web App, etc.) with current status. Useful for resolving component IDs at workflow setup.
Action
Update Statuspage Incident
Adds an update post to an existing incident. For "investigating → identified → monitoring → resolved" lifecycle updates posted automatically.
Update Statuspage Component in Statuspage — start free