ActionStatuspageUpdated September 2026

How do I update a Statuspage incident?

Short answer: You can update statuspage incident in Statuspage by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Statuspage Update Statuspage Incident action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Update Statuspage Incident in Statuspage — start free All 4 Statuspage actions

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

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.

Triggered by

Apps that pair well as the trigger for Update Statuspage Incident.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Statuspage

2 Google Sheets triggers

HubSpot → Statuspage

18 HubSpot triggers

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 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 Incident support batch operations?

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

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 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.

Update Statuspage Incident in Statuspage — start free