Statuspage
Publish to an Atlassian Statuspage — set component statuses, open and update incidents, and manage subscribers and metrics.
About
Statuspage ships in the w6w first-party pack. It declares 12 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.statuspage- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Monitoring & Observability · Communication · DevOps & Infrastructure
Overview
Statuspage is how a company tells its own customers what’s working and what isn’t, and this app is the publishing side of that: set a component’s status, open an incident and move the components it affects in the same step, post updates as an incident develops, and resolve it while restoring what it broke.
Notifying subscribers is treated as a decision, not a default — every action that can email, text or push an update leaves that off unless a workflow turns it on explicitly, so an automated first post doesn’t page an entire customer base off a single flapping check. A companion action lists who’s actually watching a page or a specific component, which is useful for knowing the size of an audience before deciding whether an update is worth sending to it. Publishing a value to a metric graph is included too, for feeding an existing uptime or performance chart from monitoring data a workflow already has.
Creating or removing subscribers, deleting an incident outright, and page branding or settings all stay out of scope — a status page is meant to be an honest public record, and this app is built to keep it one rather than to rewrite it.
Build with Statuspage
Three routes to the same 12 actions. The Workflow tab is generated from Statuspage's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Create component
component-create Add a component to the page. Names are not unique, so re-running creates a duplicate — and without `showcase` it is invisible to customers however red it goes.
List component groups
component-group-list The page's component groups. A group's status is derived from its members, not set — so changing a group means changing a component inside it.
List components
component-list Components with their ids and current statuses — the lookup every write needs, and the cheap way to check whether a change is needed at all.
Set component status
component-status-set Change one component's status. Note this posts NO update and notifies nobody — use Create Incident when customers should be told why.
Create incident
incident-create Open an incident and move its components in one request. Subscriber notifications are OFF by default — an automated first post should not page every customer.
Get incident
incident-get One incident with its full update timeline — what customers were told, when, and whether each update was actually delivered.
List incidents
incident-list Incidents on a page. `unresolved` answers 'is something already open' — the check that prevents duplicate incidents for one outage.
Resolve incident
incident-resolve Close an incident and return its components to operational in the same request — which is the step most often forgotten, leaving a resolved page covered in red dots.
Update incident
incident-update Post an update to an open incident. A PATCH with a body appends to the timeline and is what subscribers receive — one without changes the status silently.
Add a metric data point
metric-data-add Publish a value to a custom metric's graph. Timestamps are Unix SECONDS — milliseconds land the point fifty thousand years out, silently.
List pages
page-list Pages this API key can reach, with their ids and public URLs. The only call needing no page id, and the answer to why a write 404s.
List subscribers
subscriber-list Who receives notifications, and how. Worth reading before enabling delivery — this count is the blast radius of a notified incident update.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Statuspage's real ids.
{
"manifestVersion": "2",
"name": "statuspage-example",
"steps": [
{
"id": "component-create",
"uses": {
"app": "io.w6w.statuspage",
"action": "component-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"name": "<name>"
}
}
]
}Here are some of the things you can do
-
Create component
performcomponent-create -
List component groups
readcomponent-group-list -
List components
readcomponent-list -
Set component status
performcomponent-status-set -
Create incident
performincident-create
+7 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Statuspage, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Statuspage. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "component-create",
payload: {
name: "<value>",
// description: "<value>",
// status: "<value>",
// groupId: "<value>",
// showcase: "<value>",
// onlyShowIfDegraded: "<value>",
// pageId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action component-create --payload '{"name":"<value>"}'Give an AI agent Statuspage — without giving it Statuspage's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.statuspage#component-create",
"input": {
"name": "<name>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Statuspage connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Statuspage's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Statuspage itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Statuspage declares its own checks, so its health is a property of the app rather than something the host guesses at.
Statuspage platform status
Atlassian's own Statuspage. Worth watching precisely because an outage here silences the channel a workflow would use to report every other outage.