Microsoft To Do

· #155 most-used

Every to-do, acted on — not just listed

ProductivityProjectsSchedulingCommunicationAutomation

Microsoft To Do is Microsoft's cloud task manager: personal lists, due dates, and reminders that sync across every device. Connect it to Actionist and your agents can create tasks the moment work appears, complete them when it ships, and react to every status change — turning a simple checklist tool into an active part of your automation stack.

Average time saved
10 hours
per person · per month
1 workdays back

Eliminates manual work. Agents handle the repetitive task of manually transcribing action items from emails, messages, and meeting notes into the correct To Do lists.

Schedule

What your Microsoft To Do agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs
7Agents at work
24/7Always on
Agents
TueThu
Tue
Wed
Thu
7a
8a
9a
10a
11a
12p
1p
2p
3p
4p
5p
6p
Multi-app workflows

Microsoft To Do × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows
9Apps spanned
~14 hrsSaved / week
6Personas served
For customer success
Featured4 apps

Support ticket resolved, onboarding task closed

When a support email confirms a customer's onboarding issue is resolved, your agent reads the open tasks in the client's Microsoft To Do onboarding list, marks the blocking item complete, and posts a concise resolution summary in the account's Slack channel—then drops a 48-hour check-in on Google Calendar so the CSM follows up before the customer has a chance to forget the fix.

~3 hrs / week

Time saved for your team — every week, on autopilot

The flow
Trigger·When a resolution email arrives in Gmail for an open onboarding account
Result
Mark blocking task as completePost resolution summary to account channelCreate 48-hour follow-up check-in event
The win
Saved per run
18 min
Runs / week
~10×
Zero dropped follow-ups
Driven byCustomer Support Agent
ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

  • Sales
    18 min / week
    Manual follow-up logging

    After each prospect call, reps spend 18 minutes/week manually creating follow-up tasks and copying CRM notes into To Do lists.

    Sales Agent
    0 min
    Agent files every follow-up instantly

    The agent reads the call outcome from HubSpot and creates the correct follow-up task in the rep's To Do list within seconds of the call ending.

  • Marketing
    13 min / week
    Campaign checklist setup

    Before each campaign launch, marketers manually re-create the same task checklist in To Do — 13 minutes per campaign.

    Marketing Agent
    0 min
    Agent scaffolds launch tasks on approval

    When a campaign is approved in HubSpot, the agent creates the full launch checklist in the marketing To Do list automatically.

  • Customer Support
    18 min / week
    Open ticket task filing

    Support reps spend 18 minutes/week copying open ticket details from the helpdesk into personal To Do tasks so nothing slips through overnight.

    Customer Support Agent
    0 min
    Agent mirrors tickets to tasks automatically

    When a ticket is assigned, the agent creates the corresponding To Do task with the ticket link in the notes — no copy-paste required.

  • Human Resources
    7 min / week
    Onboarding task list setup

    HR manually re-creates the onboarding To Do list for each new hire — 7 minutes per hire across checklists and due dates.

    Human Resources Agent
    0 min
    Agent generates onboarding list on offer acceptance

    When an offer is accepted in the HR system, the agent creates a personalised onboarding task list with deadlines set to the start date.

  • Finance
    13 min / week
    Approval task filing

    Finance team members spend 13 minutes/week manually creating To Do tasks for budget approvals that arrive by email or Slack.

    Finance Agent
    0 min
    Agent creates approval tasks from inbound requests

    When a budget request lands in the designated Slack channel, the agent creates a prioritised approval task with the deadline and amount in the notes.

  • Operations
    25 min / week
    Exception triage task creation

    Ops coordinators spend 25 minutes/week manually logging exception rows from tracking sheets into actionable To Do tasks.

    Operations Agent
    0 min
    Agent creates triage tasks on every exception flag

    When an exception row appears in the ops sheet, the agent creates a triage task in under five seconds — no manual transcription, no delay.

  • Legal
    6 min / week
    Contract review scheduling

    Legal staff spend 6 minutes/week manually creating review tasks for incoming contracts and setting due dates based on urgency.

    Legal Agent
    0 min
    Agent queues contracts for review on receipt

    When a new contract arrives in Google Drive, the agent creates a dated review task in the Legal To Do list with the document linked directly.

+ 100s of other Microsoft To Do automations
Average monthly
10 hrs / person / month
Average monthly
10 hrs / person / month
Calculator

Calculate what your team saves

Team size
10 people
Hourly rate
$20 / hr
Hours saved / week
25
Hours saved / year
1,250
Annual ROI
$25,000

Based on Microsoft To Do's typical team usage — the visible tasks plus a few other automations the agent runs: ~2.5 hrs / person / week of admin work automated.

Connect

How to plug Microsoft To Do into Actionist

Pick the connection method that suits your environment.

The fastest path. Install the mcp-microsoft-todo MCP server and the agent reaches your Microsoft To Do lists through a permissioned Microsoft Graph OAuth handshake — no tokens to copy, no scopes to guess.

1
Open the Apps tab

Find Microsoft To Do in the Apps library and click Connect. MCP is selected by default.

2
Authorise in Microsoft To Do

A browser window opens to Microsoft's login page. Sign in with your Microsoft account, grant the requested Graph permissions (Tasks.ReadWrite, User.Read), and return to Actionist.

3
Test the connection

Actionist runs a read-only call to verify the handshake. You're ready.

Actions

15 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

6 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

Skills

Skills that pair with Microsoft To Do

Reusable agent skills that work well alongside this app.

Microsoft To Do

Manages task lists, tasks, checklist items, and linked resources in Microsoft To Do via managed OAuth — no token handling required.

MCP servers

MCP servers that work with Microsoft To Do

Connect Actionist to MCP servers built for or around this app.

mcp-microsoft-todo
Official

MCP server for Microsoft To Do via Microsoft Graph using MSAL device code flow — no client secret needed for personal accounts.

FAQs

Questions about Microsoft To Do + Actionist

How do I connect Microsoft To Do to Actionist?
Open the Apps tab, find Microsoft To Do, and click Connect. The MCP method is selected by default — a browser window opens to Microsoft's sign-in page where you grant the required Graph permissions (Tasks.ReadWrite, User.Read). Actionist runs a test call to verify the connection before enabling the integration.
What Microsoft account permissions does the agent need?
The agent requires the Tasks.ReadWrite and User.Read Microsoft Graph delegated permissions. These let it create, read, update, and complete tasks and lists on your behalf. No admin consent is required for personal Microsoft accounts; work or school accounts may need an Azure AD admin to pre-approve Tasks.ReadWrite depending on your organisation's tenant policy.
Can Actionist work with tasks across multiple To Do lists at once?
Yes. The agent can read and write across all lists in your account simultaneously. When you define a workflow, you specify the target list by name or ID. For bulk operations — like a morning briefing — the agent reads all lists in one call and filters by due date or status. There is no per-list limit imposed by the integration.
What kinds of automation work well with Microsoft To Do?
Microsoft To Do works best for personal and team task management automation: creating tasks from inbound emails or messages, marking tasks complete when work ships in another tool, scaffolding project checklists when a deal closes or a sprint starts, and routing triage tasks when exceptions appear in ops trackers. Because To Do syncs across devices, any task the agent creates is immediately visible on the user's phone and desktop.
How do I avoid duplicate tasks when multiple triggers fire?
Use the Find or Create Task action as the first write step in any workflow. The agent searches for a task matching the target title in the target list before creating one — if it already exists, the workflow continues without creating a duplicate. For idempotency across separate runs, include a unique identifier (ticket ID, deal ID, date) in the task title pattern so the search is deterministic.
Does the Updated Task trigger fire for every field change?
Yes — Updated Task fires whenever any property of a task changes: title, due date, importance, completion status, or notes. To avoid unnecessary agent runs, scope your workflow to filter on the specific field that matters. For example, check the completion status in the first step and exit early if the update was to a different field. This prevents a single task edit from triggering multiple downstream actions unintentionally.
Can the agent manage shared or assigned tasks, not just my own?
The agent operates under your Microsoft account's permissions. For tasks in shared lists where you have access, it can read, create, update, and complete items. For tasks assigned to other users within Microsoft 365 shared lists, the agent can update the task record but cannot act as the other user. If your organisation uses Microsoft Planner for team task management, that requires a separate integration.
Are there rate limits I should know about when running frequent automations?
Microsoft Graph enforces per-user throttling on the Tasks API at approximately 10,000 requests per 10 minutes for read operations and 5,000 for writes. For most automation workflows — even high-frequency ones like processing 50 tickets per hour — you will not hit these limits. If you run bulk operations over thousands of tasks in a short window, add a brief pause between batches. Actionist surfaces a throttle warning in the run log if the API returns a 429 response.