Todoist
Manage Todoist tasks, projects, sections, comments, and labels via the REST v2 API.
About
Todoist ships in the w6w first-party pack. It declares 14 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.todoist- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Productivity
Overview
Todoist is a task manager, and this app is the everyday task-management loop from a workflow: create, read, update, close and reopen tasks, manage the projects and sections that organize them, add comments, and read labels.
Closing and reopening a task, and deleting a task or a project, map onto Todoist’s own lightweight completion model, so a workflow can mark something done without a full update call. This app covers the REST v2 surface, which is the everyday task and project workflow; Todoist’s separate Sync API — used for bulk operations, reminders and quick natural-language task entry — isn’t reached here, since task placement (which project, section, or parent task) is already expressible directly at creation time.
This is a straightforward, focused app: a workflow that needs to turn an external event into a Todoist task, update one as work progresses, or read back a project’s open items has everything it needs, without the bulk-sync machinery Todoist offers for its own native clients.
Build with Todoist
Three routes to the same 14 actions. The Workflow tab is generated from Todoist'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.
Get Many Tasks
task-get-many List active tasks, optionally filtered by project, section, label, or query.
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 Todoist's real ids.
{
"manifestVersion": "2",
"name": "todoist-example",
"steps": [
{
"id": "comment-create",
"uses": {
"app": "io.w6w.todoist",
"action": "comment-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"content": "<content>"
}
}
]
}Here are some of the things you can do
-
Create Comment
performcomment-create -
Get Many Comments
readcomment-get-many -
Get Many Labels
readlabel-get-many -
Create Project
performproject-create -
Get Many Projects
readproject-get-many
+9 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 Todoist, 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 Todoist. 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: "task-create",
payload: {
content: "<value>",
// description: "<value>",
// projectId: "<value>",
// sectionId: "<value>",
// parentId: "<value>",
// order: "<value>",
// labels: "<value>",
// priority: "<value>",
// dueString: "<value>",
// dueDate: "<value>",
// dueDatetime: "<value>",
// dueLang: "<value>",
// assigneeId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action task-create --payload '{"content":"<value>"}'Give an AI agent Todoist — without giving it Todoist'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.todoist#comment-create",
"input": {
"content": "<content>"
}
}
}
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 Todoist 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
Todoist'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. Todoist itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Todoist declares its own checks, so its health is a property of the app rather than something the host guesses at.
Todoist platform status
Instatus rollup for status.todoist.net (/summary.json): overall `page.status` plus any open incidents. Unauthenticated and unsigned.