Move Card: 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
Card ID cardId	string	Required	Card ID. Example: 5abbe4b7ddc1b351ef961414
Destination List ID idList	string	Required	Trello list ID — 24-char hex. Find via List Lists on a board.
Destination Board ID (optional, for cross-board moves) idBoard	string	Optional	Destination Board ID (optional, for cross-board moves). Example: 5abbe4b7...
Position pos	options	Optional	Position. Options: Top, Bottom

Sample request

{
  "cardId": "e.g. 5abbe4b7ddc1b351ef961414",
  "idList": "e.g. 5abbe4b7...",
  "idBoard": "e.g. 5abbe4b7...",
  "pos": "{{trigger.pos}}"
}

Returns

{
  "id": "card123",
  "name": "My Card",
  "idList": "list456"
}

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

FAQ

Questions about Move Card.

What does the Move Card action do in Trello?

Moves a Trello card to a different list (the canonical Kanban stage-change action). Often used to auto-advance cards based on external state (PR merged, customer reply, etc.).

What inputs does Move Card require?

Required: Card ID, Destination 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 Move Card support batch operations?

Yes. Run Move Card 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