Microsoft To Do integration

What it does

The Microsoft To Do integration moves task management work for your clients into TaskJuice without anyone signing into the To Do web app by hand. Connect a client's Microsoft 365 (or personal Microsoft) account once and you can read every task list, list and filter tasks inside a list, create brand new tasks with body, importance, status, due date, reminders, and categories, update an existing task to flip its status or change any field, delete a task, and start a workflow whenever a new task is added to a list or whenever a task is marked complete.

Connect a Microsoft To Do account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Microsoft To Do and click Connect.
3. Sign in with the Microsoft work, school, or personal account whose To Do data you want to manage on behalf of your client.
4. Grant the requested scopes (read and write access to tasks plus the basic profile scope).
5. TaskJuice returns you to the workspace with the connection ready to use in any workflow.

To revoke access at any time, visit My Apps and consents for work and school accounts, or Microsoft account privacy for personal accounts, and remove the TaskJuice entry.

Triggers

• microsoft-todo/new-task polls a chosen task list on a configurable interval and emits one activation per cycle containing every task that was created since the previous cycle. Drop a Loop node downstream to process each task individually, or feed the array straight into a digest.
• microsoft-todo/task-completed polls a chosen task list on a configurable interval and emits one activation per cycle containing every task whose status moved to completed since the previous cycle.

Actions

• microsoft-todo/list-lists returns the task lists owned by or shared with the connected account, with cursor pagination via @odata.nextLink.
• microsoft-todo/list-tasks returns tasks inside a chosen task list, with optional OData filter, select, orderby, and pagination via @odata.nextLink.
• microsoft-todo/get-task returns a single task by ID, optionally projecting a subset of properties via OData $select.
• microsoft-todo/create-task creates a new task with title, body, importance, status, due date, reminder, and categories.
• microsoft-todo/update-task updates one or more fields on an existing task, most commonly flipping status to completed or adjusting due dates.
• microsoft-todo/delete-task permanently removes a task from a list.

Known limitations

• Microsoft Graph supports change notifications for some resources, but the To Do task resource is not currently supported for subscriptions. The new-task and task-completed triggers therefore poll on a configurable interval (60 seconds minimum, five minutes by default), so latency is bounded by the chosen interval rather than instant.
• Microsoft Graph applies per-application and per-tenant throttling. When a 429 is returned, TaskJuice surfaces it as a retryable rate-limit error and respects the recommended backoff window.
• All actions and triggers require the Tasks.ReadWrite scope. The integration does not split read and write into separate scopes because creating, updating, and deleting tasks share that single permission in the Graph permission model.
• Personal Microsoft accounts and work or school accounts share the same scope vocabulary, but tenant administrators can disable specific permissions. If the OAuth consent screen omits a scope, the corresponding actions will fail with a permission-denied error at runtime.