List Lists: Trello 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
Board ID board_id	string	Required	Board ID. Example: board123
Filter filter	options	Optional	Filter. Options: Open, Closed, All

Sample request

{
  "board_id": "e.g. board123",
  "filter": "{{trigger.filter}}"
}

Returns

[
  {
    "id": "list123",
    "pos": 1,
    "name": "To Do"
  },
  {
    "id": "list456",
    "pos": 2,
    "name": "Doing"
  },
  {
    "id": "list789",
    "pos": 3,
    "name": "Done"
  }
]

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

FAQ

Questions about List Lists.

What does the List Lists action do in Trello?

Lists all lists on a Trello board with their name and position. Required step before creating a card, since cards live in lists.

What inputs does List Lists require?

Required: Board 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 Trello 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 Lists support batch operations?

Yes. Run List Lists inside a Loop node to process arrays. Tiny Command handles Trello's rate limits automatically so you don't have to throttle manually.

More actions