Resources · Make integration

Microsoft To Do Make integrationAutomate Microsoft To Do with Make.

Tired of copying requests into your task lists by hand? The Microsoft To Do Make integration gives you 16 modules: 1 trigger, 11 actions and 4 searches. This guide is for people who know To Do well but are new to Make, and it walks you from connecting your account to a working first scenario.

Try the Microsoft To Do integration on Make See the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Microsoft To Do Make integration do for you?

The Microsoft To Do Make integration links your To Do account to Make so that tasks and lists get created, updated, completed or removed by a scenario, which is the automation you build in Make as a chain of bricks called modules. It can also watch your tasks and start a scenario when one is created or modified.

Requests that turn into tasks on their own. A message, a form entry or a row in a spreadsheet comes in through another app, and Create a Task drops it into the right list with its title already written. Nobody has to retype anything.

A clean board when a project closes. Search Tasks finds what still sits in a list, Complete a Task ticks it off, and Delete a List removes the list once the project is archived elsewhere.

A follow up on what slipped. Search Overdue Tasks returns the late items, so a scenario can send them to a chat channel or a report instead of leaving them buried in the app.

The official documentation lists no connection prerequisite and no numbered limit for this app. When a listed module does not cover your need, Make an API Call reaches the rest of the API with the same connection. The same app also exists in n8n: see the Microsoft To Do n8n integration and our n8n vs Make comparison. To learn the editor properly, the Make training starts from zero.

Connect

How do you connect Microsoft To Do to Make?

01
Add a To Do module
Open a scenario, click the +, search for Microsoft To Do and pick any of its modules. In the module panel, click Create a connection. A connection is your To Do account linked to Make once, then reused by every To Do module.
02
Name the connection
This step is optional, but a clear name helps later. If you link a personal account and a work account, call them by what they hold so you never send a client task into the wrong place.
03
Authorize and save
A Microsoft window opens and asks you to let Make access your account. Accept, come back to Make, and click Save. The module can now read your lists and offer them in its fields.

First scenario

Your first scenario with Microsoft To Do

GoalWhen a request with a file arrives in another app, Make creates a task in Microsoft To Do and attaches the file to it.

01
Create the scenario
On the Scenarios page, create a new scenario and click the +. The first module is the app where your requests land: a form tool, an inbox or a shared folder.
02
Add Create a Task
Click the + on the right of that first module, search for Microsoft To Do and pick Create a Task. Select your connection, then choose the list Make proposes once it can read your account.
03
Map the request
Fill the task fields with data from the first module: the subject of the message becomes the title, for example. Each item passing between modules is a bundle, one request per bundle here.
04
Attach the file
Add Add an Attachment after the task, point it to the task Make just created and to the file coming from the first module. The file now sits inside the task.
05
Test with Run once
Click Run once and send yourself a test request. Open each module bubble to read the bundle it received, then check the new task in To Do.
06
Schedule and switch on
Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Triggers

What starts a Microsoft To Do scenario

1 module starts a scenario when something happens in Microsoft To Do. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Microsoft To Do as soon as it happens.

Microsoft To Do1Watch Tasks

Watch Tasks

Scheduled trigger

In Make“Triggers when a new task is created or modified.”

Watch Tasks gives your scenario a starting point inside To Do: it picks up every task that was created or modified since the last check and passes each one on as a bundle.

How it fires

it is a scheduled trigger, so Make checks the app on the scenario's schedule, every 15 minutes by default and never more often than that on the Free plan.

When to use it

when a task edited by a colleague should be copied to a shared tracker or announced in a team channel.

Watch out

a modified task comes back too, so a scenario that edits the same tasks it watches will pick up its own changes.

Modules

Every Microsoft To Do module, explained

Microsoft To Do gives you 15 modules in 4 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Task

7 modules

Microsoft To Do1

Search Tasks

In Make“Searches for Microsoft To-do tasks by a filter.”

You get back the tasks that match a filter, one bundle per task, ready to be updated, completed or copied somewhere else in the next module.

When to use it

before a bulk change, to gather every open task of a list that belongs to a finished project.

Watch out

a search can return zero, one or many tasks, so the modules that follow run once per result.

Microsoft To Do2

Search Overdue Tasks

In Make“Searches for overdue Microsoft To-do tasks with a filter.”

This search hands you only the tasks that are overdue, filtered the way you need, which saves you from sorting dates yourself in the scenario.

When to use it

to build a short list of late items and send it to the person in charge or to a team channel.

Watch out

when nothing is late, the search returns no bundle and the rest of the scenario simply does not run.

Microsoft To Do3

Get a Task

Action

In Make“Gets the details of a Microsoft To-do task.”

Get a Task reads the full detail of one task you already know, so every later module works from the complete, current version of that task.

When to use it

right after Watch Tasks, when you need the latest state of the task before deciding what to do with it.

Microsoft To Do4

Create a Task

Action

In Make“Creates a new task with a file attachment (File size should not be above 3MB).”

This action writes a new task into the list you choose, with the content mapped from any earlier module, so requests stop living only in email threads.

When to use it

each time a form, a ticket or a message should become something a person has to do.

Watch out

run it once per request, or a search placed before it will create one task per result it finds.

Microsoft To Do5

Update a Task

Action

In Make“Updates an existing task.”

Update a Task changes an existing task in place, so it keeps following what happens in your other tools without anyone editing it by hand.

When to use it

when a deadline moves in your project tool and the To Do task should reflect the change.

Watch out

the module needs the task to target, usually taken from Search Tasks or Watch Tasks.

Microsoft To Do6

Delete a Task

Action

In Make“Deletes a task.”

This module removes a task for good. Your lists stay short once an item no longer matters anywhere.

When to use it

when the request behind the task is cancelled in the source app, and a finished state would be misleading.

Watch out

Make offers no undo, so try it on a throwaway list with Run once first.

Microsoft To Do7

Complete a Task

Action

In Make“Completes a task.”

Complete a Task marks a task as done, which closes it for the team while keeping a record of it, unlike a deletion.

When to use it

when an invoice gets paid or a ticket gets closed elsewhere and the matching To Do item should follow.

Watch out

prefer it to Delete a Task whenever someone may want to see later what was done.

List

5 modules

Microsoft To Do8

Search Lists

In Make“Searches for Microsoft To-do lists by a filter.”

Search Lists returns the lists of the account that match your filter, one bundle each, so a scenario can find where to write without a hard coded choice.

When to use it

when each client or project has its own list and the scenario must pick the right one from a name.

Watch out

no match means no bundle, so plan what happens when the list does not exist yet.

Microsoft To Do9

Get a List

Action

In Make“Gets the details of a Microsoft To-do list.”

With this module you read the details of a single list you already identified, which is handy to check its name before writing tasks into it.

When to use it

after Search Lists, or with a list chosen in the module, when a later step needs the list's own information.

Microsoft To Do10

Create a List

Action

In Make“Creates a new list.”

Create a List opens a brand new list in To Do, which gives each new project or client its own place from the first minute.

When to use it

when a deal is signed in your CRM and the onboarding steps need a dedicated list.

Watch out

run Search Lists first if the scenario may fire twice for the same project, or you will end up with duplicate lists.

Microsoft To Do11

Update a List

Action

In Make“Updates an existing list.”

This action renames or edits an existing list, so its label stays in step with the project or client name used in your other tools.

When to use it

when a project changes name or status and everyone should still find its tasks under the right label.

Watch out

target the list through Search Lists or Get a List rather than by guessing it.

Microsoft To Do12

Delete a List

Action

In Make“Deletes a list.”

Delete a List removes a whole list from your account, which clears the app once a project is archived elsewhere and nobody needs it anymore.

When to use it

at the end of a closing scenario, after the useful tasks were completed or copied out.

Watch out

this is the most destructive module of the app, so keep a filter or a manual approval step before it.

Attachment

2 modules

Microsoft To Do13

List Attachments

In Make“Get a list of attachment objects attached to an Outlook task.”

List Attachments gives you the files attached to a task, one bundle per file, so they can be copied to a storage app or sent along with a message.

When to use it

after Watch Tasks, to save the documents a colleague added to a task into the project folder.

Watch out

a task without files returns nothing, and the following modules skip it.

Microsoft To Do14

Add an Attachment

Action

In Make“Adds an attachment to a Microsoft To-do Task (The file must not be larger than 3MB).”

This module puts a file inside an existing task, so the person who picks it up has the document right there instead of hunting through email.

When to use it

after Create a Task, to join the quote, the brief or the form export that triggered the request.

Watch out

map a real file from an earlier module, not just its name or link.

Other

1 module

Microsoft To Do15

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you call any endpoint of the To Do API from your scenario, with the connection you already set up, when the other modules stop short.

When to use it

for an operation the listed modules do not offer, once you have read the API reference of Microsoft.

Watch out

you write the request yourself, so test it with Run once and read the answer before relying on it.

Need help

Need help automating Microsoft To Do with Make?

A person reads every message.

FAQ

Questions people ask about Microsoft To Do and Make

01Is the Microsoft To Do Make integration free?

Yes, Microsoft To Do is a standard app in Make, so you can use it on the Free plan. That plan gives you 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on a bundle.

02What do you need to connect Microsoft To Do to Make?

A Microsoft account that uses To Do and a Make account. The official documentation lists no other prerequisite. You add any To Do module, click Create a connection, give it a name if you like, authorize Make in the Microsoft window and click Save. Every To Do module in your scenarios then reuses that connection, so you only do this once per account. If you manage both a personal and a work account, create one connection for each and name them clearly.

03Does Microsoft To Do notify Make instantly when a task changes?

No. Watch Tasks is a scheduled trigger: Make checks your tasks on the scenario's schedule and collects everything created or modified since the previous check. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans can go down to 1 minute. The app has no instant trigger in Make, so if you need a faster start, the scenario has to begin in another app that calls Make directly.

04What if a Microsoft To Do module you need is missing in Make?

Use Make an API Call. It sends any request to the To Do API with the connection you already have, so you can reach what the 15 other modules do not cover. You build the request yourself from the Microsoft API reference, then test it with Run once and read the returned bundle before going further. The documentation gives no numbered limit for this app, so check the answer carefully the first time you run a new call.

05Should you use Make or n8n for Microsoft To Do?

It depends on the tool your team already uses. Microsoft To Do has an n8n node as well as its 16 Make modules, so both can create, update and search tasks. If your other scenarios already run in Make, keeping To Do there means one editor, one set of connections and one place to check runs. If your workflows live in n8n, the n8n node keeps everything together. The choice follows your existing setup more than the app itself.

Add a To Do module

Name the connection

Authorize and save

Create the scenario

Add Create a Task

Map the request

Attach the file

Test with Run once

Schedule and switch on

Need help automating Microsoft To Do with Make?