Microsoft To Do
Manage Microsoft To Do task lists, tasks, checklist items, and linked resources via the Microsoft Graph To Do API.
About
Microsoft To Do ships in the w6w first-party pack. It declares 19 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.microsoft-todo- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Productivity · Project Management
Overview
Microsoft To Do is Microsoft’s personal task manager, and this app manages its task lists, tasks, checklist items and linked resources through the Microsoft Graph To Do API — the same API behind every official To Do client.
It covers the everyday task lifecycle: creating, updating and completing tasks, and reopening one by unmarking it, organized into task lists a workflow can also create and manage. Checklist items add subtasks within a single task, and a linked resource attaches a back-pointer to whatever caused the task in the first place — an email, a ticket, a CRM record — so a workflow can round-trip between a task and the system that spawned it.
Change-tracking actions let a workflow poll for what changed since its last run, including deletions a simple timestamp filter can’t detect, which is useful for keeping an external system in sync with someone’s task list without re-reading everything each time. This app is scoped to Microsoft To Do specifically — it does not reach into Microsoft Planner’s team task boards, a related but separate product with its own API.
Build with Microsoft To Do
Three routes to the same 19 actions. The Workflow tab is generated from Microsoft To Do'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.
Complete Task
complete-task Mark a task as completed. Use Update Task with status `notStarted` to reopen one.
Create Linked Resource
create-linked-resource Link a task back to the record it came from, so the task shows where it originated.
Delete Task
delete-task Delete a task. Use Complete Task instead when the task was actually finished.
Delete Task List
delete-task-list Delete a To Do list and every task in it. The built-in Tasks and Flagged email lists cannot be deleted.
Get Task
get-task Read one task, optionally expanding its checklist items and linked resources inline.
List Linked Resources
list-linked-resources List the linked resources on a task — the records it was created from.
List Task Changes
list-task-changes Track additions, updates and deletions to the tasks in one list using Graph delta query.
List Task List Changes
list-task-list-changes Track additions, updates and deletions to the user's To Do lists using Graph delta query.
List Task Lists
list-task-lists List the signed-in user's To Do lists, including the built-in Tasks and Flagged email lists and any lists shared with them.
List Tasks
list-tasks List the tasks in one To Do list. There is no cross-list endpoint — call this once per list.
Update Task
update-task Update a task. Only the fields you set are sent, so the rest are left untouched.
Update Task List
update-task-list Rename a To Do list. The built-in Tasks and Flagged email lists cannot be renamed.
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 Microsoft To Do's real ids.
{
"manifestVersion": "2",
"name": "microsoft-todo-example",
"steps": [
{
"id": "complete-task",
"uses": {
"app": "io.w6w.microsoft-todo",
"action": "complete-task",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"taskList": "<taskList>",
"task": "<task>"
}
}
]
}Here are some of the things you can do
-
Complete Task
performcomplete-task -
Create Checklist Item
performcreate-checklist-item -
Create Linked Resource
performcreate-linked-resource -
Create Task
performcreate-task -
Create Task List
performcreate-task-list
+14 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 Microsoft To Do, 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 Microsoft To Do. 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: "create-task",
payload: {
taskList: "<value>",
title: "<value>",
// body: "<value>",
// bodyContentType: "<value>",
// status: "<value>",
// importance: "<value>",
// categories: "<value>",
// dueDateTime: "<value>",
// startDateTime: "<value>",
// reminderDateTime: "<value>",
// isReminderOn: "<value>",
// completedDateTime: "<value>",
// timeZone: "<value>",
// recurrence: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action create-task --payload '{"taskList":"<value>","title":"<value>"}'Give an AI agent Microsoft To Do — without giving it Microsoft To Do'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.microsoft-todo#complete-task",
"input": {
"taskList": "<taskList>",
"task": "<task>"
}
}
}
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 Microsoft To Do 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
Microsoft To Do'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. Microsoft To Do itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Microsoft To Do declares its own checks, so its health is a property of the app rather than something the host guesses at.