Short answer: Drop the "Todoist → Create Task" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Task Content content | string | Required | The task title (supports Markdown) |
Description description | string | Optional | Description. Example: Milk, eggs, bread... |
Project ID project_id | string | Optional | Todoist project ID — numeric string. Find via List Projects. |
Priority priority | options | Optional | Priority. Options: Normal, High, Very High, Urgent |
Due Date due_string | string | Optional | Due date in natural language (e.g. 'tomorrow', 'next Monday', 'Jan 15') or YYYY-MM-DD format. Leave empty for no due date. |
Labels labels | string | Optional | Comma-separated label names |
{"content": "e.g. Buy groceries","description": "e.g. Milk, eggs, bread...","project_id": "e.g. 2345678901","priority": "{{trigger.priority}}","due_string": "e.g. tomorrow, 2026-01-15, next Monday"}
{"id": "7654321","due": {"date": "2025-01-16","string": "tomorrow"},"url": "https://todoist.com/showTask?id=7654321","content": "Buy groceries","priority": 1}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.