Pipedream Todoist steps in n8n

Todoist workflows on Pipedream are personal automations: an email, a Slack message or a calendar event becomes a task, a completed task gets logged somewhere. n8n's native Todoist node handles tasks, projects, sections, comments and labels.

The n8n side

Todoist node (n8n-nodes-base.todoist). The current node version (2.x) has six resources; the docs page still describes only Task:

Resource	Operations
Task	Close, Create, Delete, Get, Get Many, Move, Quick Add, Reopen, Update
Project	Archive, Create, Delete, Get, Get Collaborators, Get Many, Unarchive, Update
Section	Create, Delete, Get, Get Many, Update
Comment	Create, Delete, Get, Get Many, Update
Label	Create, Delete, Get, Get Many, Update
Reminder	Create, Delete, Get Many, Update

Task → Create takes content, project, section, labels, priority and a due string or date. There is no Todoist trigger node.

What maps where

Pipedream (app todoist)	In n8n	Status
Create Task	Task → Create	manual
Update Task	Task → Update	manual
Mark Task as Completed	Task → Close	manual
Find Task, List Uncompleted Tasks	Task → Get Many with a filter	manual
Move Task To Section	Task → Move	manual
Create Project	Project → Create	manual
Create Task Comment	Comment → Create	manual
New Task, New Completed Task, New or Modified Task (polling)	Schedule Trigger + Task → Get Many + Remove Duplicates	manual
New Project, New Section (polling)	Schedule Trigger + Project / Section → Get Many	manual

Todoist actions are not in the converter's mapped list. Each step is a placeholder that keeps its props (content, project ID, due string) in a comment, and the report lists the Todoist credential to create.

Todoist credentials in n8n

• API key: Todoist → Settings → Integrations → Developer → API token.
• OAuth2: on n8n Cloud connect in the browser; self-hosted n8n needs an app in the Todoist App Management Console with n8n's redirect URL.

Rebuilding a polling source

Pipedream's Todoist sources checked for new items on a timer, so a Schedule Trigger gives the same behaviour:

1. Schedule Trigger every 5 or 15 minutes.
2. Task → Get Many (project or filter as in the source).
3. Remove Duplicates, mode "Remove items processed in previous executions", key = task ID.

For completed tasks, call the completed-tasks endpoint via HTTP Request, since Get Many returns only active tasks.

Typical migration: starred email to task

Pipedream: Gmail New Starred Email → Todoist Create Task (project Inbox, due "today"). n8n: Gmail Trigger (label STARRED) → Todoist → Task → Create (Content = subject, Description = link to the email, Due String = today).

Todoist migration pitfalls

• API v1. Todoist consolidated its REST and Sync APIs into API v1; older code steps calling rest/v2 or sync/v9 endpoints should be checked against the current docs before reuse.
• Sync limits. Per user, up to 1,000 partial sync and 100 full sync requests per 15 minutes; up to 100 commands per batch request.
• Due strings are parsed in the language set in the request; "tomorrow 9am" works in English.
• IDs are strings. Keep project and task IDs as text.

How to move your Todoist workflows

1. Export from Pipedream.
2. Upload on /convert; the free report lists every Todoist step and its props.
3. Get the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

More: Pipedream schedules in n8n. Related: Asana, Notion, Google Calendar.