Workflowy
Capture, edit, organise and export WorkFlowy outline nodes: bullets, todos, notes, mirrors and the Inbox.
About
Workflowy 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.workflowy- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Productivity
Overview
WorkFlowy is an infinitely nestable outliner: every bullet is a node that can hold children, a note, a todo state and a header style. This app covers the whole of WorkFlowy’s public API v1, so a workflow can capture a thought into the Inbox, drop a task onto today’s calendar node, tick it off when the work is done, or sweep the whole outline out for backup.
Nodes can be created, read, updated, listed by parent, moved, completed, uncompleted and deleted, and any node can be mirrored under a second parent so its content shows in two places at once. Parents are addressed the way WorkFlowy addresses them: a full node id, the 12-character short id from a WorkFlowy URL, a shortcut key you defined, or a built-in target such as inbox, today, tomorrow or a YYYY-MM-DD calendar day.
A targets listing shows which shortcut keys exist on the account, and a full-outline export returns every node as a flat list for backups or analysis.
Build with Workflowy
Three routes to the same 12 actions. The Workflow tab is generated from Workflowy'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 Node
node-create Create a bullet, todo, header or other node under a parent, the Inbox or a calendar day.
Create Mirror
node-mirror-create Mirror a node under another parent so its content appears in both places.
Update Node
node-update Change a node's text, layout or note. Fields you leave empty are not changed.
Export All Nodes
nodes-export Export the whole outline as a flat list. Limited to 1 request per minute.
List Targets
targets-list List the shortcut keys and system targets (such as inbox) usable as parent ids.
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 Workflowy's real ids.
{
"manifestVersion": "2",
"name": "workflowy-example",
"steps": [
{
"id": "node-complete",
"uses": {
"app": "io.w6w.workflowy",
"action": "node-complete",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"id": "<id>"
}
}
]
}Here are some of the things you can do
-
Complete Node
performnode-complete -
Create Node
performnode-create -
Get Node
readnode-get -
List Child Nodes
readnode-list -
Create Mirror
performnode-mirror-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 Workflowy, 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 Workflowy. 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: "node-complete",
payload: {
id: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action node-complete --payload '{"id":"<value>"}'Give an AI agent Workflowy — without giving it Workflowy'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.workflowy#node-complete",
"input": {
"id": "<id>"
}
}
}
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 Workflowy 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
Workflowy'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. Workflowy itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Workflowy declares its own checks, so its health is a property of the app rather than something the host guesses at.
WorkFlowy platform status
Component status from status.workflowy.com; the API component decides the verdict.