Taskade
Manage Taskade workspaces, folders, projects, tasks, assignees, due dates, notes and AI agents through the Taskade REST API v1.
About
Taskade ships in the w6w first-party pack. It declares 35 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.taskade- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Project Management · Productivity
Overview
Taskade is a collaborative workspace where projects are outlines of tasks that teams, AI agents and automations work on together. This app connects a workflow to the Taskade REST API (v1) with a Personal Access Token.
A workflow can list the workspaces a token can see, the folders (subspaces) inside a workspace and the projects, AI agents, media and project templates inside a folder. It can read, create, copy, complete and restore projects; list, read, create, edit, move, complete, reopen and delete the tasks inside a project; read and set a task’s assignees, due date and note; and read a project’s members, custom fields and share link. It can also read an AI agent and its conversations.
Taskade answers every failure with an ok: false envelope carrying a stable code, and this app reports that code. Health checks verify the token, whether the API answers, the per-token rate-limit headroom and Taskade’s own status page.
Build with Taskade
Three routes to the same 35 actions. The Workflow tab is generated from Taskade'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.
List Folder Project Templates
folder-template-list List the project templates available in a folder.
Create Project
project-create Create a project in a folder from Markdown content (headings and lists become tasks).
Create Project From Template
project-create-from-template Create a project in a folder from a project template.
Create Project in Workspace
project-create-in-workspace Create a project directly in a workspace from Markdown content.
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 Taskade's real ids.
{
"manifestVersion": "2",
"name": "taskade-example",
"steps": [
{
"id": "agent-conversation-list",
"uses": {
"app": "io.w6w.taskade",
"action": "agent-conversation-list",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"agentId": "<agentId>"
}
}
]
}Here are some of the things you can do
-
List Agent Conversations
searchagent-conversation-list -
Get Agent
readagent-get -
List Folder Agents
searchfolder-agent-list -
List Folders
searchfolder-list -
List Folder Media
searchfolder-media-list
+30 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 Taskade, 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 Taskade. 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: "agent-conversation-list",
payload: {
agentId: "<value>",
// limit: "<value>",
// page: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action agent-conversation-list --payload '{"agentId":"<value>"}'Give an AI agent Taskade — without giving it Taskade'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.taskade#agent-conversation-list",
"input": {
"agentId": "<agentId>"
}
}
}
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 Taskade 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
Taskade'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. Taskade itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Taskade declares its own checks, so its health is a property of the app rather than something the host guesses at.
Taskade platform status
The "App" component from Taskade's Statuspage, plus its other components for visibility.
API reachable
Unauthenticated GET /workspaces. Taskade's `ok:false` UNAUTHORIZED envelope passes: it proves the application is answering.
API rate-limit headroom
Requests remaining in the current window, read off the x-rate-limit-* headers.