List Cards: 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
List ID list_id	string	Required	List ID. Example: list123
Filter filter	options	Optional	Filter. Options: Open, Closed, All

Sample request

{
  "list_id": "e.g. list123",
  "filter": "{{trigger.filter}}"
}

Returns

[
  {
    "id": "card123",
    "due": "2025-06-30T17:00:00Z",
    "name": "Task 1",
    "idList": "list123",
    "shortUrl": "https://trello.com/c/abc123"
  }
]

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

FAQ

Questions about List Cards.

What does the List Cards action do in Trello?

Lists cards on a Trello board or in a specific list. Used for sprint reviews, board exports, or daily-digest generation.

What inputs does List Cards require?

Required: List 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 Cards support batch operations?

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