--- title: "Microsoft To Do Integration" description: "Manage Microsoft To Do task lists and tasks from your flows: create tasks with due dates and reminders, complete or reopen them, and manage checklist steps. Agents capture work and confirm before escalating a task to a person." url: https://flowrunner.ai/integrations/microsoft-todo date_modified: 2026-08-01T02:40:32-07:00 --- # Microsoft To Do [Productivity](https://flowrunner.ai/integrations/category/project-management-productivity) Manage Microsoft To Do task lists and tasks from your flows: create tasks with due dates and reminders, complete or reopen them, and manage checklist steps. Agents capture work and confirm before escalating a task to a person. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 15 actions · OAuth · available [Microsoft To Do website](https://microsoft.com/) · [Platform Documentation](https://learn.microsoft.com/en-us/graph/api/resources/todo-overview) · Capability data verified 2026-07-14 1. An actionable email arrives in the connected user's inbox 2. Agent reads the sender, subject, and the request in the body 3. Agent confirms the message warrants a task 4. Agent decides the list, due date, and importance for the task 5. Agent creates the task with a due date and high importance 6. Agent records the source so the task carries its context 7. A task that should page someone is routed for a person to confirm the escalation ## What This Integration Enables FlowRunner agents use Microsoft To Do to capture and structure work as decisions, not manual entry. An agent can create a task with a due date, reminder, importance, categories, and recurrence, complete or reopen it as a workflow moves, and provision a per-project list scaffolded with templated tasks and checklist steps. It can add checklist items to an existing task as work is broken down, and post a daily digest of outstanding work. The routine capture and scaffolding run on their own. The escalation, where a task should page a person, is where the agent stops to ask. ### Without FlowRunner **Inbox as task list**: Requests live in the inbox until someone copies them into To Do **Missed deadlines**: Tasks get created without due dates or reminders, so they slip **Manual project setup**: A new project's task list and steps are built by hand each time ### With FlowRunner **Emails become tasks**: Actionable messages are captured with a due date the moment they arrive **Reminders keep pace**: Tasks carry due dates, reminders, and importance so nothing is forgotten **Lists scaffold themselves**: The agent provisions a project list and its checklist steps from a template ## Use Case Scenarios ### Email to Task with a Reminder An actionable email arrives. The agent reads it, picks the right list, and creates a task with Create Task, setting a due date and high importance so nothing slips through the inbox. It records the sender and subject in the body so the context travels with the task. ### Project Scaffolding A new project entry appears. The agent calls Create Task List to stand up the project's list, then Create Task for each planned item, adding checklist steps with Add Checklist Item for the subtasks. Because the scaffold comes from a template, every project starts with the same structure. ### Daily Digest with an Escalation Gate On a schedule, the agent lists outstanding work with List Tasks filtered to not-completed and posts a digest to the team. When a task is overdue and high importance, the agent proposes paging the owner. Before it escalates beyond the routine digest, it confirms the escalation with a lead so a person decides whether the task really warrants an interrupt. ## Human-in-Loop Highlight When an overdue, high-importance task crosses the line from "include in the digest" to "page the owner now", the agent does not decide to interrupt someone on its own. An escalation is a judgment call about whether the cost of waiting outweighs the cost of the interrupt. The agent pauses and routes to a team lead through their preferred channel: "Task '\[Task\]' is \[N\] days overdue and marked high importance. Page the owner now, keep it in the daily digest, or reassign?" The lead decides, and the agent acts from there. Routine capture and digests run on their own; interrupting a person reaches a person first. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 15 actions ### Task Lists 4 - **Create Task List** Creates a task list with a display name. Used to provision a per-project list. - **List Task Lists** Lists the user's task lists with their names and well-known identifiers. Used to resolve which list to file work in. - **Update Task List** Renames a task list. Well-known lists like the default cannot be renamed. Used to keep list names in sync. - **Delete Task List** Permanently deletes a task list and its tasks. Well-known lists cannot be deleted. Used in cleanup. ### Tasks 7 - **Create Task** Creates a task with a body, due date, reminder, importance, categories, and optional recurrence. Used to turn a message or event into scheduled work. - **Get Task** Retrieves a single task with its status, importance, due date, reminder, and recurrence. Used to read current state before acting. - **List Tasks** Lists tasks in a list, optionally filtered by completion status, with paging. Used to build a digest or find work to process. - **Update Task** Updates a task's properties, changing only the fields provided. Used to reschedule or edit a task. - **Complete Task** Marks a task completed, creating the next occurrence for recurring tasks. Used to mark work done. - **Reopen Task** Reopens a completed task and clears its completion date. Used to reverse a premature close. - **Delete Task** Permanently deletes a task and its checklist items. Used in cleanup. ### Checklist Items 4 - **Add Checklist Item** Adds a checklist item (subtask) to a task. Used to break a task into steps. - **List Checklist Items** Lists the checklist items on a task with their checked state. Used to review a task's steps. - **Check Or Uncheck Checklist Item** Marks a checklist item checked or unchecked. Used to progress a task's steps. - **Delete Checklist Item** Permanently deletes a checklist item from a task. Used in cleanup. ## Frequently Asked Questions ### What can FlowRunner do with Microsoft To Do? FlowRunner agents can run Create Task List, List Task Lists, and Update Task List in Microsoft To Do, plus 12 more actions. ### Does connecting Microsoft To Do to FlowRunner require OAuth? Yes. Microsoft To Do connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Microsoft To Do trigger a FlowRunner workflow automatically? Microsoft To Do doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Microsoft To Do?** This integration exposes Microsoft To Do to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/microsoft-todo. Site index: https://flowrunner.ai/llms.txt