List Comments: 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
Task ID task_id	string	Optional	ID of the task to get comments for. Provide either task_id OR project_id, not both.
Project ID project_id	string	Optional	ID of the project to get comments for. Provide either task_id OR project_id, not both.

Sample request

{
  "task_id": "e.g. 7654321",
  "project_id": "e.g. 2345678901"
}

Returns

[
  {
    "id": "comm123",
    "content": "Updated the requirements doc.",
    "task_id": "7654321",
    "posted_at": "2025-01-15T12:00:00Z"
  },
  {
    "id": "comm456",
    "content": "Looks good to me!",
    "task_id": "7654321",
    "posted_at": "2025-01-15T14:30:00Z"
  }
]

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

FAQ

Questions about List Comments.

What does the List Comments action do in Todoist?

Lists comments on a specific Todoist task or project. Use to build a discussion timeline or to export conversation history.

What inputs does List Comments require?

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

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