- Integrations
- /
- Statuspage
- /
- Actions
- /
- Update Statuspage Incident
ActionStatuspageUpdated May 2026
How do I update a Statuspage incident?
Short answer: Drop the "Statuspage → Update Statuspage Incident" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
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
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 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.
Send update statuspage incident from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.