ActionTodoistUpdated September 2026

How do I fetch a Todoist section by ID?

Short answer: You can get section in Todoist by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Todoist Get Section action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get Section in Todoist — start free All 27 Todoist actions

Get Section in Todoist — start free

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
Section ID section_id	string	Required	Todoist section ID — numeric string. Find via List Sections.

Sample request

{
  "section_id": "e.g. 7025"
}

Returns

{
  "id": "456",
  "name": "In Progress",
  "order": 2,
  "project_id": "123"
}

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

Triggered by

Apps that pair well as the trigger for Get Section.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Todoist

2 Google Sheets triggers

HubSpot → Todoist

18 HubSpot triggers

FAQ

Questions about Get Section.

What does the Get Section action do in Todoist?

Returns a single section by ID with its name, order, and parent project.

What inputs does Get Section require?

Required: Section ID. 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 run history shows the failed step with its input and the error message Todoist returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Get Section support batch operations?

Run Get Section inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Todoist's rate limits.

More actions