List Sections: 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	Optional	Filter sections by project. Leave empty to list all sections.

Sample request

{
  "project_id": "e.g. 2345678901"
}

Returns

[
  {
    "id": "sec123",
    "name": "In Progress",
    "order": 1,
    "project_id": "2345678901"
  },
  {
    "id": "sec456",
    "name": "Done",
    "order": 2,
    "project_id": "2345678901"
  }
]

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

FAQ

Questions about List Sections.

What does the List Sections action do in Todoist?

Lists all sections in a Todoist project. Use it to populate a section picker before creating or moving a task.

What inputs does List Sections require?

List Sections has no required inputs. Sensible defaults are applied if you leave fields blank.

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 List Sections support batch operations?

Yes. Run List Sections 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