List Tasks: 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	Project ID. e.g. "Filter by project (optional)"
Label label	string	Optional	Label. e.g. "Filter by label name (optional)"
Filter filter	string	Optional	Todoist filter query (e.g. 'today', 'overdue', 'p1')

Sample request

{
  "project_id": "Filter by project (optional)",
  "label": "Filter by label name (optional)",
  "filter": "e.g. today & #Work"
}

Returns

{
  "results": [
    {
      "id": "123",
      "due": {
        "date": "2025-01-16"
      },
      "content": "Buy milk",
      "priority": 1
    }
  ]
}

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

FAQ

Questions about List Tasks.

What does the List Tasks action do in Todoist?

Lists active (uncompleted) Todoist tasks, optionally filtered by project, section, label, or Todoist's filter query language. Common in daily-digest and review workflows.

What inputs does List Tasks require?

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

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