Update Statuspage Component: Statuspage action

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.

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. Tiny Command handles Statuspage's rate limits automatically so you don't have to throttle manually.

More actions