Create 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
Name name	string	Required	API latency elevated
Status status	options	Required	—
Impact impact_override	options	Optional	—
Incident Body body	string	Optional	Message body content. Plain text unless the API specifies HTML/markdown.
Affected Component IDs component_ids	array	Optional	—

Sample request

{
  "name": "API latency elevated",
  "status": "{{trigger.status}}",
  "impact_override": "{{trigger.impact_override}}",
  "body": "e.g. Hi there, thanks for reaching out.",
  "component_ids": "{{trigger.component_ids}}"
}

Returns

{
  "id": "inc_abc",
  "name": "API latency",
  "impact": "minor",
  "status": "investigating",
  "shortlink": "https://stspg.io/abc"
}

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

FAQ

Questions about Create Statuspage Incident.

What does the Create Statuspage Incident action do in Statuspage?

Opens an incident with status, affected components, body. For "monitoring detected outage → auto-post to status page" workflows that keep customers informed.

What inputs does Create Statuspage Incident require?

Required: Name, 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 Create Statuspage Incident support batch operations?

Yes. Run Create 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