Todoist Automations: 7 Setups That Fit GTD

The best Todoist automations are the ones that move items you have already thought about, and leave the thinking alone. The honest conclusion, up front: of everything the rule builder can do, about seven setups earn a place in a GTD system, four of them actively damage it, and a good half of what people ask automation for is really a saved filter they have not built yet.

If you already run projects, labels and filters in Todoist, nothing here asks you to rebuild. It asks you to judge each rule by one question: does it remove a decision, or remove a keystroke? Automate the keystroke. Never the decision.

What Todoist Automations Actually Do (And Where They Stop)

A rule is a trigger plus an action. Something happens to a task (it gets created in a particular project, it gets assigned, a label goes on, a date passes) and Todoist does something in response (adds a label, moves it, sets a date, posts a message, creates another task). That is the whole model. Everything else is presentation.

Todoist ships ready-made automation ideas you can preview and install rather than building from scratch, which is useful for seeing which triggers exist on your account before you design anything. Install one and read it afterwards. Most of the prebuilt ideas are perfectly sensible; two or three of them will date your tasks in ways you did not ask for, and you want to know that before the rule has been running for a fortnight.

Native rules versus Zapier, Make and the rest

Check the native integration first. Todoist integrations with Slack, Google Calendar, Gmail and Outlook already cover the jobs most people reach for a connector to do: turning a message into a task, pushing dated items onto a calendar, sending mail into a project by email address. If a first-party integration covers it, use that. Fewer moving parts, fewer silent failures.

Zapier or Make is still the only route when the other end of the job is somewhere Todoist does not reach: a CRM, a billing system, a form, a database in Notion, a filtered view in a client’s tool. That is a real need and worth paying for when it exists. Paying a monthly fee so a Slack emoji can create a task is not.

Rules an assistant can write, and why you write them down anyway

Todoist’s AI features can set up and adjust rules from a prompt, which means a rule can exist in your account that you did not type out and cannot quite remember agreeing to. That is the part people underestimate. A rule you cannot name is a rule you cannot audit, and an unauditable rule is exactly how a task with a date you did not choose ends up at the top of today.

Keep a plain-text note, one line per rule: what it fires on, what it does, why you added it. Six lines in a file called rules.txt. If a task appears and you cannot match it to a line, delete the rule that made it. The same discipline applies to any assistant you let near your lists, which is the thread running through our guide to the GTD jobs ChatGPT does well and the ones it ruins.

Plans, limits and availability move

Rule counts, trigger types and which integrations are included vary by plan, and Todoist has changed the packaging more than once. Before you design a workflow around a trigger, open the current Todoist pricing page and confirm it is on your tier at the time you are reading this. Designing a weekly review around a feature you do not have is a miserable afternoon.

Where Automation Belongs in the Five GTD Steps

David Allen’s five steps are capture, clarify, organise, reflect and engage, and they are not equally mechanical. You can read the method straight from the source at the official Getting Things Done site, but the short version for this purpose: two of those steps are sorting and surfacing, and software is good at both.

Organising is moving a clarified item to the right list with the right label. Reflecting is pulling together a view at a set interval so you can see what has gone stale. Both are rules work. Capture benefits from automation only in one direction, which is getting the thought out of your head and into one place quickly.

Clarifying is the step automation ruins. Deciding the next physical action on an open loop is the work that makes the whole system function, and a rule that files an item called “Website”into a project as a task has not organised anything. It has hidden undone thinking behind a tidy-looking list. You will scroll past it for three weeks and feel vaguely guilty, which is the opposite of what the list is for.

Four Todoist Automations That Protect Capture and Clarifying

1. One-way email into the inbox

Send or forward actionable mail to your Todoist inbox email address and clarify it during triage. One direction only. Do not enable a two-way mailbox sync that mirrors flagged mail back and forth, because then the promise lives in two places and you stop trusting both. Judge this one on time-to-captured, not on cleverness: a forward takes about three seconds and the item lands once. If you want more routes into the same single inbox, the quick capture routes worth setting up are worth a read alongside this.

2. Voice and assistant capture with nothing attached

Set up voice capture so a spoken thought lands in the Todoist inbox with no project, no date and no priority. Resist the temptation to have the assistant guess a project. Raw capture should stay raw, because the moment a rule assigns a project it also implies the item has been clarified, and it has not. The five-second standard for this is covered in more depth in our piece on capturing every idea in under five seconds.

3. A source label on anything arriving from a connector

Any task created by chat, email or a connector gets a label such as @from-slack or @from-mail. It costs nothing and it pays for itself the first time you open a task that says “send over the figures”with no idea who asked or when. At review you can trace the item back to its origin instead of reconstructing it from half a memory.

4. An ageing flag on unclarified inbox items

Anything sitting in the inbox past a set number of days gets flagged, so a silent pile becomes a visible queue. If your plan does not offer an age-based trigger, a saved filter does the same job: something along the lines of #Inbox & created before: -7 days, checked against Todoist’s current filter syntax. Seven days is my threshold. Pick yours and keep it.

Three Automations for Organising, Waiting For and the Weekly Review

5. Delegation applies Waiting For and a check-back

In a shared project, when a task is assigned to a colleague, the rule applies a @waiting-for label and sets a check-back date five working days out. Now the handover appears in your weekly review rather than in your memory at 11pm. If assignment is not available as a trigger on your plan, do it by hand at triage: the two keystrokes matter less than the habit.

6. Context labels applied by project or section

Errands, Calls, Computer and Low Energy, applied automatically to tasks created in the projects or sections where they always apply. The point is the view it produces. A Saturday morning filter for @errands that returns six items you can do in one trip is usable. A mixed list of 40 is a decoration.

7. A recurring stalled-projects review task

One recurring task on review day, pointing at a filter that shows projects with no dated or labelled next action. Todoist has no native stalled-projects view, so the rule’s job is to put the question in front of you at a fixed time. Notice that the automation here is a prompt, not a fix. You still do the clarifying.

Four Automations That Quietly Break Trust in Your Lists

Auto-dating everything

A due date is a commitment to a specific day. Rules that stamp a date on anything that merely needs doing soon build a red overdue wall, and a wall you see every morning is a wall you learn to ignore. Once red means nothing, the genuinely time-bound item is invisible. Use dates sparingly; our guide on deciding what to do next without dating everything goes further into that.

Recurring tasks standing in for a tickler

Repeating tasks are not automation and they are not a tickler file. Using a weekly repeat to nudge yourself about a project manufactures a backlog of overdue items instead of forcing one decision. Someday/maybe lists and the weekly review carry that load.

Two-way syncs

The most common self-inflicted wound. Mail, chat or a second task app mirrored in both directions produces duplicate open loops and a second inbox you half believe in. One trusted inbox, one direction in.

Automatic priority and auto-rescheduling

If you cannot explain why a task is sitting at the top of today, the list has stopped being a trusted system and become a suggestion engine. Smart scheduling is pleasant to watch and corrosive to run. You stop arguing with it, then you stop reading it.

When a Filter Beats an Automation (And When Another App Does It Better)

Most requests for automation are requests for a view. Build the filter first. A filter costs nothing, breaks nothing, creates no tasks and can be deleted without residue, and if the filter solves it you are done. Automate only the labelling that the filter depends on.

Todoist filters handle date ranges, labels, projects, assignee and combinations of those perfectly well. Where they run out is availability and shape: blocked and deferred items, grouping, custom sort order, the kind of view you would assemble with the OmniFocus rule builder. If you want the comparison in detail, see our guide to custom OmniFocus perspectives and the wider rundown of Mac tools that build a working GTD system.

The honest trade-off: Todoist buys cross-platform reach and real collaboration, OmniFocus and Things buy sharper review views. Both are defensible. Pick your automation strategy to suit the app you are actually staying with, because the exit cost of switching task managers is paid in trust, not in export files.

How to Add One Automation Without Wrecking Your Setup

Treat each rule the way Allen’s natural planning model treats a project. Purpose: what problem does this fix. Outcome: what should the list look like afterwards. Then build the rule, and only then.

1. One rule at a time, two-week trial. Note on day one what it was meant to fix. If at the end of the fortnight you cannot point at the improvement, delete it.
2. Name rules so their output is traceable. Any task a rule creates should be identifiable at a glance. Anything you cannot account for goes.
3. Add an automations line to the weekly review checklist. What fired, what created noise, what can go. Two minutes, once a week.
4. Keep project support material in notes, not in generated tasks. Reference material belongs in comments or a note-taking app, so the action lists stay short enough to scan.

Nobody should run all seven of these. Pick the one that fixes the thing annoying you this month, give it a fortnight, and keep the ones that survive. The best Todoist automations are boring, named, few in number, and never asked to do your thinking for you. If you want the wider frame around the rules, read our walkthrough of building a personal productivity system that lasts next.

Frequently Asked Questions

Do Todoist automations need a paid plan?

Rule counts and available triggers depend on your tier, and Todoist has changed its packaging more than once. Check the current pricing page before you design a workflow around a specific trigger. Saved filters and labels, which do most of the work described here, are a cheaper place to start.

Can a saved filter do the job instead of a Todoist automation?

Very often, yes. If what you want is to see a particular set of tasks at a particular moment, that is a view, and a filter gives it to you without creating anything. Build the filter first and automate only the labelling the filter relies on.

Will AI-assisted automations add or reschedule tasks without asking?

A rule created or edited through an assistant can act on your lists exactly like one you built by hand, so read what it was set to do before you leave it running. Keep a plain written record of every rule. If a task appears and you cannot match it to a line in that record, remove the rule that produced it.

Which Todoist automations are worth running for a weekly review?

Three: the Waiting For label with a dated check-back on delegation, context labels applied by project or section, and a recurring review task pointing at a filter for projects with no next action. Those three put the right questions in front of you. They do not answer them.

Is Zapier still worth paying for now that Todoist has built-in automations?

Only when the other end of the job sits outside Todoist’s own integrations, such as a CRM, a form or a billing system. If a native Slack, calendar or email integration already covers it, use that instead. Fewer connections, fewer silent failures at the worst possible moment.