Create Section: Todoist action

Inputs

The fields this action accepts.

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.
Section Name name	string	Required	Section Name. Example: In Progress
Order order	string	Optional	Position of the section among other sections

Sample request

{
  "project_id": "e.g. 2345678901",
  "name": "e.g. In Progress",
  "order": "e.g. 1"
}

Returns

{
  "id": "sec789",
  "name": "In Progress",
  "order": 1,
  "project_id": "2345678901"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Create Section.

What does the Create Section action do in Todoist?

Creates a new section inside a Todoist project. Sections are how board-view columns are organized.

What inputs does Create Section require?

Required: Project ID, Section Name. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Todoist returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Create Section support batch operations?

Yes. Run Create Section inside a Loop node to process arrays. Tiny Command handles Todoist's rate limits automatically so you don't have to throttle manually.

More actions