ActionTodoistUpdated June 2026

How do I fetch a Todoist section by ID?

Short answer: Drop the "Todoist → Get Section" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 27 Todoist actions

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 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 Get Section support batch operations?

Yes. Run Get 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