Update Statuspage Incident: 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
Incident ID incident_id	string	Required	—
New status status	string	Optional	—
Update message body	string	Optional	Message body content. Plain text unless the API specifies HTML/markdown.

Sample request

{
  "incident_id": "{{trigger.incident_id}}",
  "status": "{{trigger.status}}",
  "body": "e.g. Hi there, thanks for reaching out."
}

Returns

{
  "id": "inc_abc",
  "status": "resolved"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Update Statuspage Incident.

What does the Update Statuspage Incident action do in Statuspage?

Adds an update post to an existing incident. For "investigating → identified → monitoring → resolved" lifecycle updates posted automatically.

What inputs does Update Statuspage Incident require?

Required: Incident ID. 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 Incident support batch operations?

Yes. Run Update Statuspage Incident 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