Short answer: Drop the "Todoist → Update Label" 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 |
|---|---|---|---|
Label ID label_id | string | Required | The Label ID assigned by Todoist. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Name name | string | Optional | Name. e.g. "New label name" |
Color color | string | Optional | Color. Example: berry_red, blue |
Favorite is_favorite | boolean | Optional | Favorite |
{"label_id": "{{trigger.label_id}}","name": "New label name","color": "e.g. berry_red, blue","is_favorite": "{{trigger.is_favorite}}"}
{"id": "100","name": "work","color": "blue","order": 1,"is_favorite": true}
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.