Todoist n8n integrationAutomate Todoist with n8n.

Closing a task from a workflow does what ticking the checkbox does in the app: the task leaves the active list and stops showing up in filters.

• Task ID: the identifier of the task to close, usually carried over from an earlier node as {{ $json.id }}.

The structured way to add work: every field is set explicitly instead of being read from a sentence, which keeps the result predictable when the data comes from another system.

• Project Name or ID: the destination project, chosen from the list or given as an ID.
• Content: the task text itself.
• Additional Fields: 13 optional fields, among them Due String (a due date written in plain words, read in local time), Due Date in YYYY-MM-DD, Priority from 1 (normal) to 4 (urgent) and Assignee ID for a shared task.

Deletion is permanent and the node has no undo operation, so it belongs in cleanup flows rather than in day-to-day routing.

• Task ID: the task to remove, often the identifier stored when the workflow created it.

A single task comes back with its fields, which is how a workflow checks the current state before deciding what to do next.

• Task ID: the identifier of the task to read, often pulled from a message or a database row as {{ $json.taskId }}.

This is the reporting operation of the node: one call, every task that matches, ready to be counted, formatted or exported.

• Return All: on, n8n walks the pages of the API and brings back everything; off, Limit caps how many tasks come back.
• Filters: Filter takes any supported Todoist filter, while Project Name or ID, Section Name or ID, Label Name or ID and IDs (a comma separated list) narrow the result further.
• Lang: the language the filter is written in, when it is not English.

Moving leaves the content alone: same task, same identifier, new project, and a new section inside it when needed.

• Task ID: the task to move.
• Project Name or ID: the destination project, required even when only the section changes.
• Section Name or ID: optional, the section the task lands in.

Quick Add reads natural language the way the app does, so one written sentence becomes a complete task.

• Text: the sentence to parse. The due date is written in free form, a project starts with #, a label with @, an assignee with +, a priority reads as p1, a deadline sits between {}, and everything after // becomes the description.
• Additional Fields: Note adds the content of a note, Reminder takes a date in free form text, and Auto Reminder adds the default reminder when the due date has a time.

The mirror of Close: a completed task returns to the active list and shows up again in filters and digests.

• Task ID: the closed task to bring back.

Only the fields you fill in are sent, so a workflow can push a new due date or a new priority without rewriting the task.

• Task ID: the task to edit.
• Update Fields: Content and Description for the text, Due String, Due Date or Due Date Time for the timing, plus Priority, Label Names, Assignee ID and Deadline Date in YYYY-MM-DD.

Archiving takes the project out of the active list without deleting anything it holds. It is the end of engagement gesture.

• Project ID: the project to archive, accepted as a string or as a number.

Every client, campaign or sprint can get its own container, created by the workflow with the same naming rule each time.

• Name: the name of the project.
• Additional Fields: Color picks from the Todoist palette (berry_red, teal, lavender and the rest), Parent ID nests it under an existing project, Is Favorite pins it, and View Style opens it as list or board.

Deleting a project cannot be undone from the node: no operation brings it back, and nothing in n8n keeps a copy of what was inside. The step is better placed behind a human approval than in an automatic branch.

• Project ID: the project to delete, given as a string or as a number.

Turning an identifier into a readable record is the job here: one project in, its data out.

• Project ID: the project to read, as a string or as a number.

The people who share a project come back here, and nowhere else in the node. It is the only operation that answers who, rather than what.

• Project ID: the shared project to inspect, as a string or as a number.

One call, every project in the account. The operation takes no parameter at all: no filter, no pagination setting, nothing to configure, so sorting, counting and filtering all happen in the next node of the workflow.

An archived project comes back among the active ones. This is the counterpart of Archive and the quickest way to reopen work that was closed too early.

• Project ID: the archived project to restore.

Renaming, recoloring or pinning a project happens through this operation, and only the fields you fill in travel.

• Project ID: the project to edit.
• Update Fields: Name, Color, Is Favorite and View Style (list or board).

Sections split a project into stages, and creating them from a workflow gives every new project the same layout.

• Project Name or ID: the project the section is added to.
• Name: the name of the section.
• Additional Fields: Order sets where the section sits among the others.

Removing a section changes the structure of a project, so the operation tends to clean up a template rather than run every day.

• Section ID: the section to delete, usually read from Get many sections earlier in the run.

Confirming that a section identifier still points to something is the practical use of this read, and the returned record gives the next node its name.

• Section ID: the section to read.

Sections come back as a list, across the account or inside a single project, which gives a workflow the map it needs before it moves anything.

• Filters: Project Name or ID restricts the list to one project, chosen from the list or passed through an expression.

The node exposes a single editable field on a section, and that is its name. Nothing else about a section can be changed from a workflow.

• Section ID: the section to rename.
• Update Fields: Name, the new section name.

Posts a comment on a task that already exists in Todoist and returns that comment with an identifier of its own.

• Task ID: the task the comment lands on, almost always mapped from an earlier node with an expression, the n8n syntax that pulls a value out of the incoming item, such as {{ $json.id }}.
• Content: the text of the comment, usually assembled from the data that came in (an order number, a form answer).

Removes one comment for good. The node answers with a confirmation and not with the text it just erased, so anything worth keeping gets read first, with Get a comment.

• Comment ID: the identifier of the comment itself, not the one of the task it hangs under. It comes from Get many comments, or from the step that wrote the comment earlier in the same execution.

Fetches one precise comment from its identifier and hands the content to the nodes that follow.

• Comment ID: the identifier of the comment to read. Chain the operation after Get many comments when the workflow has to find the right one first.

Returns a list of comments instead of a single one, and one of the two filters below sets its scope: a single task, or every comment in a project.

• Task ID: inside Filters, keeps only the comments attached to one task.
• Project ID: inside Filters, widens the read to every comment in a project.

Replaces the text of a comment that is already published. A task reporting on the same job three times a day stays readable, because the status lives in one comment rather than in a stack of them.

• Comment ID: the comment to rewrite, kept from the execution that created it.
• Content: inside Update Fields, the new text. It takes the place of the old one, so the workflow sends the complete line and not only the part that moved.

Adds a label to the Todoist account and returns the identifier that the later steps will reuse.

• Name: the name of the label, the only required field.
• Color: inside Additional Fields, a closed list of named values such as sky_blue, olive_green or magenta. A color gets picked from the list, never typed as a hex code.
• Order: where the label sits in the list; Is Favorite marks it as a favorite.

Drops a label from the account. The call has no way back: recovering the label means creating it again.

• Label ID: the identifier of the label, the one Get many labels returns. The name alone will not do.

Reads one label and returns the state Todoist holds for it.

• Label ID: the identifier of the label being looked up, stored by the step that created it or taken from a list read.

Lists every label in the account in one call, with nothing to set up first. That is how a workflow works on stable identifiers instead of trusting a name that somebody may have changed since.

Edits a label in place. Only the fields added under Update Fields travel to Todoist, so changing a color leaves the name untouched.

• Label ID: the label concerned.
• Name: its new name.
• Color: one of the values in the list, red or lavender for instance, when the meaning of the label changes.
• Order and Is Favorite: move the label up the list or put it in the favorites.

Attaches a reminder to an existing task so Todoist speaks up at the right moment.

• Task ID: the task carrying the reminder.
• Due Date Type: how the moment is written, each choice opening its own field: natural_language with Natural Language Representation (tomorrow 2pm), full_day with Date in YYYY-MM-DD, floating_time with Date Time and no timezone, fixed_timezone with Timezone like America/New_York.
• Minute Offset: under Additional Fields, fires a relative reminder that many minutes before the due date; Notify User ID points it at one person on a shared task.

Cancels a reminder without touching the task: the task stays, the notification goes away.

• Reminder ID: the identifier of the reminder, returned by Get many reminders or by the step that set it up.

Brings back every reminder the account holds, with no parameter to fill in first. The node offers no filter either, so the sorting and the picking happen in the nodes that follow.

Moves or retunes a reminder that is already in place, rather than deleting it and creating another one at the risk of losing the link to the task.

• Reminder ID: the reminder being edited.
• Due: inside Update Fields, holds the new moment at which it should fire.
• Type and Minute Offset: switch between absolute and relative, or change how many minutes before the task due date it goes off; Notify User ID passes it to somebody else.