Short answer: Drop the "Todoist → Get Project" 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 |
|---|---|---|---|
Project ID project_id | string | Required | Todoist project ID — numeric string. Find via List Projects. |
{"project_id": "e.g. 2345678901"}
{"id": "2345678901","url": "https://todoist.com/showProject?id=2345678901","name": "Work","color": "blue","view_style": "list","is_favorite": false,"is_inbox_project": false}
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.