Resources · Make integration

Todoist Make integrationAutomate Todoist with Make.

Tasks should land in Todoist on their own, not by copy and paste. The Todoist Make integration gives you 40 modules and one instant trigger to create, move and close work. This page links your account and walks you through a first scenario.

Try the Todoist integration on MakeSee the 40 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Todoist Make integration do for you?

The Todoist Make integration links your Todoist account to Make, a visual tool where you build a scenario: the automation itself, a chain of modules that each do one job. Todoist brings 40 of those modules: one trigger that reacts to new events, 33 actions and 6 searches covering tasks, projects, labels, comments, filters and sections.

Turn incoming requests into tasks. A form reply or a support email reaches Make through another app, Create a task writes it into the right project, and Create a comment keeps the original message next to it. Nobody retypes anything.

Push Todoist changes to the rest of your tools. Watch new events is an instant trigger: Todoist tells Make as soon as something happens, and the scenario can forward that change to a chat channel or a shared sheet.

Keep a clean record of the work. Export tasks as a file produces a CSV of your tasks, and Get stats returns your productivity stats, handy for a report a manager reads without opening Todoist.

One limit to know: Todoist caps how many requests it accepts. When a scenario hits that ceiling, Make shows a 429 error, and a Sleep module placed before the retry gives Todoist time to reset. The Make troubleshooting guide covers the other errors you may meet.

Todoist also has an n8n node, described on the Todoist n8n integration page, and the n8n vs Make comparison lays the two tools side by side. New to Make itself? The Make review is a good place to start.

Connect

How do you connect Todoist to Make?

  1. 01

    Add a Todoist module

    Sign in to Make, open your scenario and add any Todoist module. In its settings, click Create a connection. A connection is your Todoist account linked to Make once, then reused by every Todoist module you add later.

  2. 02

    Name it and pick extra scopes

    Give it a clear label in Connection name, for example the workspace it belongs to. Leave Additional Scopes empty unless you plan to use Make an API call: that field only adds the permissions those custom calls need.

  3. 03

    Save and allow access

    Click Save. Todoist then asks you to sign in and confirm that Make may reach your account. Once you accept, the connection appears in the module and Make can list what it finds in your Todoist.

First scenario

Your first scenario: requests that become Todoist tasks

GoalWhen a new request comes in through another app, Make creates a task in Todoist and adds the full request as a comment.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the large +. The first module is the app where requests arrive, such as your form tool or your inbox.

  2. 02

    Add Create a task

    Click the + to the right of that first module, search for Todoist and choose Create a task. Pick your connection, or click Create a connection if this is your first Todoist module.

  3. 03

    Map the request into the task

    Fill the module fields. Make offers what it can read from your account, and you drag data from the first module into the task, so the subject of the request becomes the task itself.

  4. 04

    Attach the details with a comment

    Add Create a comment after the task module. Map the task returned by the previous step and put the full request text in the comment, so the context stays with the work.

  5. 05

    Test with Run once

    Send yourself a test request, then click Run once. Each module shows the bundles it received, one bundle per item. Open them to check the task and its comment in Todoist.

  6. 06

    Schedule and switch it on

    Open the clock on the first module to set the schedule, which is every 15 minutes by default on a new scenario. Then switch the scenario on so it runs without you.

Triggers

What triggers a Todoist scenario?

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

Todoist1Watch new events

Watch new events

Instant trigger

In Make“Triggers when a new event occurs on Todoist.”

Watch new events starts your scenario the moment something new happens in your Todoist account, so the rest of the chain works on fresh data instead of an old copy. Each event travels on as a bundle, one item handed to the next module.

How it fires
instant, Todoist calls Make through a webhook as soon as it happens. That is the lightning badge on the module.
When to use it
choose it when a change in Todoist should reach another tool, like a team chat or a spreadsheet, without anyone copying it across.
Watch out
click Create a webhook before Create a connection. If the same scenario also writes to Todoist, check that its own changes do not start it again.
Modules

What can Make do in Todoist?

Todoist gives you 39 modules in 8 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Projects

5 modules
Todoist1

List projects

Search

In Make“Returns a list of new projects.”

This search pulls the projects of your account into the scenario, one bundle per project, so every module placed after it can work on each project in turn.

When to use it
when a whole portfolio needs the same treatment, such as copying every project name into a planning sheet.
Watch out
each bundle it returns runs the next modules once, and every run counts as an operation on your plan.
Todoist2

Get a project

Action

In Make“Returns information about a project”

Reads one project and hands its details to the next module, which saves you from searching through the whole list when you already know which project you mean.

When to use it
when an earlier module gives you a project and you need more of its information, for instance before writing a summary of it elsewhere.
Todoist3

Create a project

Action

In Make“Creates a new project.”

Opens a brand new project in Todoist from inside the scenario, so a new client or a new event gets its own space without anyone setting it up by hand.

When to use it
right after a deal is signed in your CRM, so the delivery team finds its project ready.
Watch out
run it once per real event, or a test run leaves duplicate projects behind.
Todoist4

Update a project

Action

In Make“Updates a project.”

Changes an existing project, so its name or settings follow what happens in your other tools and nobody has to rename it by hand later.

When to use it
when a client changes name or a job moves to a new stage and the project title should say so.
Watch out
map the right project from an earlier module; Make edits whichever project you point it at, so point carefully.
Todoist5

Delete a project

Action

In Make“Deletes a project.”

Removes a project from Todoist, which keeps the sidebar tidy once a piece of work is truly over and nothing inside it is still needed.

When to use it
at the end of a flow that has already exported or archived what the project held.
Watch out
a deletion does not come back. Test it on a throwaway project before pointing it at real ones.

Labels

5 modules
Todoist6

List labels

Search

In Make“Returns a list of labels.”

Returns the labels of your account as separate bundles, which lets a scenario check what already exists before it tags anything.

When to use it
before Create a label, to avoid adding a second label with the same name.
Watch out
an empty result is a valid answer; add a filter after the search so the next module knows what to do when nothing comes back.
Todoist7

Get a label

Action

In Make“Returns information about a label.”

Fetches the information of a single label, so the next module works with that label and nothing else instead of a full list.

When to use it
when a task or a previous step points to one label and you want its details, for example to reuse its name in a message to your team.
Todoist8

Create a label

Action

In Make“Creates a label.”

Adds a new label to Todoist, giving you a fresh tag that later tasks can carry across every project where you use it.

When to use it
when a new client, campaign or product line appears in another tool and your tasks should be tagged with it.
Watch out
run List labels first if the same name could already exist.
Todoist9

Update a label

Action

In Make“Updates a label.”

Edits a label that already exists, so a rename in your source tool shows up on every task wearing that tag without touching the tasks one by one.

When to use it
when a campaign or a product gets a new name and the label should match it.
Watch out
map the label from an earlier module rather than typing it, so the right one changes.
Todoist10

Delete a label

Action

In Make“Deletes a label.”

Takes a label out of your account for good, which clears tags nobody uses anymore and keeps the label list short.

When to use it
when a campaign or a client closes and its tag has no reason to stay.
Watch out
there is no undo. Run the scenario once on a test label before pointing it at labels your team relies on.

Tasks

10 modules
Todoist11

List uncompleted tasks

Search

In Make“Returns a list of uncompleted tasks.”

Brings back the tasks that are still open, one bundle per task, so you can build a digest or a reminder from real, unfinished work only.

When to use it
to send a manager the open items of a project, or to copy pending work into a report.
Watch out
a long list means many bundles, and every module after it runs on each of them, which adds up in operations.
Todoist12

Get a task

Action

In Make“Returns information about a task.”

Looks up one task and returns its information, which is the step to add when a module only gave you the task and you need what is inside it.

When to use it
when an earlier step, such as List uncompleted tasks, points to a task and you want its full content before sending it to a chat or a spreadsheet.
Watch out
the module needs the task from an earlier step, so map it rather than typing it.
Todoist13

Create a task

Action

In Make“Creates a task.”

Writes a new task into Todoist from anything the scenario knows: a form answer, an email, a row in a sheet. It is the module most Todoist scenarios end with.

When to use it
whenever a request lands in another tool and someone has to act on it.
Watch out
if the source can send the same item twice, add a check before it, or the task appears twice too.
Todoist14

Update a task

Action

In Make“Updates a task.”

Edits an existing task so it reflects what changed elsewhere, without anyone reopening Todoist to adjust it by hand.

When to use it
when a request is revised in the tool it came from and the matching task should carry the new wording.
Watch out
you need a reliable way to find the right task, so store its reference when you create it or look it up first.
Todoist15

Delete a task

Action

In Make“Deletes a task.”

Removes a task entirely, which suits items that should never have existed rather than work that is simply done.

When to use it
when a request is cancelled at the source and its task only adds noise to the list.
Watch out
finished work belongs with Complete a task or Close a task instead; a deleted task is gone and leaves no history.
Todoist16

Complete a task

Action

In Make“Completes a task.”

Ticks a task off from the scenario, so work finished in another tool is marked done in Todoist as well and the list tells the truth.

When to use it
when an invoice is paid or a ticket is solved elsewhere and the matching task can close.
Watch out
for a task that repeats, Complete a recurring task is the module built for that case.
Todoist17

Complete a recurring task

Action

In Make“Completes a recurring task.”

Handles a repeating task when the current round is done, so a routine chore can be checked off by the scenario instead of by a person.

When to use it
when a repeating check, such as a backup review your team logs in another app, is confirmed there first.
Watch out
use it only on tasks that actually repeat; a one-off task belongs with Complete a task.
Todoist18

Close a task

Action

In Make“Closes a task. Regular task is completed and moved to history, subtask is checked (marked as done, but not moved to history), recurring task is moved forward (due date is updated).”

Closes a task and lets Todoist pick the right outcome: a regular task is completed and moved to history, a subtask is checked without moving, and a recurring task jumps to its next due date.

When to use it
when your scenario closes tasks of mixed kinds and should not care which kind it meets.
Watch out
on a recurring task nothing disappears; only the due date moves forward.
Todoist19

Uncomplete a task

Action

In Make“Uncompletes a task.”

Reopens a task that was marked done, putting it back in the list of open work so it gets attention again.

When to use it
when a customer reopens a ticket or a delivery is rejected, and the finished task has to come back.
Watch out
the scenario needs the exact task from an earlier module, so keep its reference when the task is first created.
Todoist20

Move a task

Action

In Make“Moves a task.”

Shifts a task to another place in Todoist, which is how a scenario hands work from one team or stage to the next without duplicating it.

When to use it
when a lead turns into a client and the task should leave the sales project for the delivery one.
Watch out
map the destination from List sections or an earlier module, so the task lands where the team expects it.

Comments

5 modules
Todoist21

List comments

Search

In Make“Returns a list of comments.”

Gathers the comments of a task as separate bundles, so the discussion around the work can travel somewhere else.

When to use it
to copy a task's discussion into a report, or to hand the whole thread to someone who does not use Todoist.
Watch out
a busy thread returns many bundles, and each one runs the modules placed after it.
Todoist22

Get a comment

Action

In Make“Returns information about a comment.”

Retrieves one comment with its information, handy when a previous step points to a comment and you need its text rather than the whole thread.

When to use it
when List comments or an earlier step points to one comment and you want to forward exactly that one to a chat channel.
Todoist23

Create a comment

Action

In Make“Creates a comment.”

Posts a comment on a task, which keeps context such as an original email, a link or an answer right next to the work.

When to use it
just after Create a task, to store the full request that led to it.
Watch out
map the task returned by the earlier module, so the comment lands on the item the scenario just made.
Todoist24

Update a comment

Action

In Make“Updates a comment.”

Rewrites a comment that already exists, so a status note posted by the scenario can stay current instead of piling up new ones.

When to use it
when a scenario keeps a single status comment on a task and refreshes it as the order or ticket moves on.
Watch out
save the comment reference when you first create it, or the scenario cannot find it again.
Todoist25

Delete a comment

Action

In Make“Deletes a comment.”

Erases a comment from a task, useful for cleaning out notes that a scenario posted and that no longer apply.

When to use it
when an automatic status note was posted by mistake or has been replaced by a newer one.
Watch out
comments your colleagues wrote disappear just as easily, so aim the module only at comments your own scenario created.

Filters

4 modules
Todoist26

List filters

Search

In Make“Returns a list of filters.”

Returns the filters saved in your account, one bundle each, giving the scenario a view of the custom lists people already rely on.

When to use it
before creating or editing a filter, to see whether a similar one exists and avoid clutter.
Watch out
if the account holds no filter yet, the search returns nothing and the modules after it do not run.
Todoist27

Create a filter

Action

In Make“Creates a filter.”

Adds a saved filter to Todoist, so a new team member or a new project starts with a ready-made view of the tasks that matter.

When to use it
during onboarding, when a new person or a new client should get a dedicated view without asking anyone.
Watch out
check with List filters first, or repeated runs stack up identical filters.
Todoist28

Update a filter

Action

In Make“Updates a filter.”

Changes a saved filter, keeping the views people use aligned with how the team now works without asking each person to edit their own.

When to use it
after a label or a project is renamed by the scenario, so the filter built on it keeps showing the right tasks.
Watch out
point it at the right filter, mapped from List filters.
Todoist29

Delete a filter

Action

In Make“Deletes a filter.”

Removes a saved filter from the account, which trims views that point to projects or labels that no longer exist.

When to use it
as the last step of an offboarding flow, once the person or the client the filter served has left.
Watch out
a deleted filter cannot be restored, so test on a spare one before running it for real.

Sections

4 modules
Todoist30

List sections

Search

In Make“Returns a list of sections.”

Returns the sections that split your projects into stages, one bundle each, so the scenario can pick the right column before placing a task.

When to use it
ahead of Move a task or Create a task, when the destination section depends on the data you received.
Watch out
a project with no section returns an empty result, so plan what happens then.
Todoist31

Create a section

Action

In Make“Creates a section.”

Adds a section inside a project, giving a new stage or a new category its own block of tasks without anyone editing the project by hand.

When to use it
right after Create a project, to lay out the stages every new client project should follow.
Watch out
map the project from the earlier module so the section lands in the new project, not an old one.
Todoist32

Update a section

Action

In Make“Updates a section.”

Edits a section that is already there, so the stages of a project can follow a change of process without rebuilding the project.

When to use it
when your pipeline stages are renamed in another tool and the Todoist sections should use the same words.
Watch out
run List sections before it to find the exact section to change.
Todoist33

Delete a section

Action

In Make“Deletes a section.”

Removes a section from a project, clearing a stage the team no longer uses so the board reads clearly.

When to use it
when a process loses a step, for example once a review stage is dropped from your delivery flow.
Watch out
think about the tasks sitting in that section first; move them with Move a task before the deletion, since it cannot be undone.

Import and Export

3 modules
Todoist34

Import tasks

Action

In Make“Imports tasks into a selected project.”

Loads a batch of tasks into a project you choose, which saves you from creating a long checklist one task at a time.

When to use it
when every new client or new hire should start from the same set of tasks, dropped into their own project.
Watch out
pair it with Create a project and map the new project, so the tasks do not end up in the wrong place.
Todoist35

Export tasks as a file

Action

In Make“Exports tasks as a csv file.”

Produces a CSV file of your tasks that the next module can store or send, turning a Todoist list into a document anyone can open.

When to use it
when a closed project should leave a record in your drive, or a client asks for the list of work done.
Watch out
the Free plan handles files up to 5 MB, so keep an eye on the size of big task lists.
Todoist36

Export tasks as shareable URL

Action

In Make“Exports tasks as shareable URL.”

Creates a link to your exported tasks instead of a file, so you share the list with a click and nothing to attach.

When to use it
when the next module is an email or a chat message and a link reads better than an attachment.
Watch out
treat the link like the list itself and send it only to people who should see those tasks.

Other

3 modules
Todoist37

Upload a file

Action

In Make“Uploads a file.”

Sends a file into Todoist so it can be attached to your work, bringing a contract, a brief or a photo into the place where the task lives.

When to use it
when an email attachment or a form upload belongs with the task created from it.
Watch out
the file must come from an earlier module, and the Free plan limits files to 5 MB.
Todoist38

Get stats

Action

In Make“Returns the user's productivity stats.”

Returns your Todoist productivity stats as data the scenario can reuse, so the numbers can end up in a report instead of staying inside the app.

When to use it
when a manager wants those figures in a shared sheet or a dashboard next to other team metrics.
Watch out
the stats belong to the account behind the connection, not to the whole team.
Todoist39

Make an API call

Action

In Make“Sends a custom API call to Todoist. You can use this to call endpoints that aren’t covered by existing modules.”

Calls any endpoint of the Todoist API with the connection you already have, which covers whatever the ready-made modules leave out.

When to use it
when you need a Todoist feature that none of the other modules handles.
Watch out
the call may need extra permissions; add them in Additional Scopes when you create the connection, one for every call you plan.
Need help

Need help automating Todoist with Make?

A person reads every message.

FAQ

Todoist and Make: common questions

01Is the Todoist Make integration free?
Yes. Todoist is a standard app in Make, so its 40 modules are available from the Free plan on. The Free plan has limits you will feel quickly: 2 active scenarios, at least 15 minutes between two 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 count usage in operations, one per module run.
02What do you need to connect Todoist to Make?
A Todoist account is the only prerequisite. In any Todoist module, click Create a connection, give it a name if you like, then click Save and confirm access when Todoist asks you to sign in. The Additional Scopes field is optional and only matters for the Make an API call module. Advanced settings let you enter your own Todoist client credentials; if you go that way, the redirect URI to use is https://www.make.com/oauth/cb/todoist3. For the instant trigger, create the webhook before the connection.
03Does the Todoist trigger in Make fire instantly?
Yes. Watch new events is an instant trigger: Todoist calls Make through a webhook as soon as a new event occurs, so the scenario does not wait for a polling interval. That is why the module shows a lightning badge rather than a clock. It is also the only trigger in the Todoist app. If you want a scenario to start from something else, open it with a module of another app, or run it on a schedule and use a search such as List uncompleted tasks.
04What if a Todoist module is missing or you hit a limit?
It depends on the problem. When no module does what you need, Make an API call reaches any endpoint of the Todoist API with the same connection; add the right scopes in Additional Scopes when you set the connection up. When Make returns a 429 Too many requests error, Todoist's rate limit has been reached: place a Sleep module before retrying the request so Todoist has time to reset, and the scenario stops failing on busy runs.
05Should you use Make or n8n for Todoist?
It depends on where your other automations already run. On the Make side, Todoist comes with 40 modules, including an instant trigger and a generic API call module, and it works from the Free plan. n8n offers a Todoist node too. Neither tool wins in every case: check that the actions you need exist on the side you pick, then keep your Todoist flows in the same place as the rest of your scenarios.
Same platform

Other docs you might need on this stack.

Browse all integrations