Statuspage
Statuspage incident and component management
Statuspage (Atlassian's public-status-communication tool) is the dashboard at status.yourcompany.com that tells customers about ongoing incidents and historical uptime. Tiny Command exposes four actions, no triggers (Statuspage doesn't emit outbound webhooks for incident-state changes; for "react when ops opens an incident" workflows, fire the workflow from your alerting tool — PagerDuty, Opsgenie — and use Create Incident here as the action): Create Incident (open a public or private incident with affected components, status, body), Update Incident (add an update post — "investigating → identified → monitoring → resolved" is the standard lifecycle), List Components (the system surfaces, like API, Database, Web App, that customers see status for), Update Component Status (change a single component's status — operational, degraded_performance, partial_outage, major_outage). The connection uses a Statuspage API key from Manage Page → API. Most incident workflows pair Create Incident with Update Component Status — the incident text tells customers what's happening, the component status colours the system-overview matrix.
Do anything Statuspage can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| 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. |
| List Statuspage Components | Returns the configured system components (API, Database, Web App, etc.) with current status. Useful for resolving component IDs at workflow setup. |
| 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 | Adds an update post to an existing incident. For "investigating → identified → monitoring → resolved" lifecycle updates posted automatically. |
Pre-built Statuspage workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Statuspage once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Statuspage field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Statuspage integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Statuspage to Tiny Command?
What Statuspage triggers does Tiny Command support?
What Statuspage actions can I run from a workflow?
Is the Statuspage integration real-time?
Do I need to write code to use Statuspage with Tiny Command?
How much does the Statuspage integration cost?
More developer tools apps people connect.
Same category as Statuspage, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Statuspage.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
