Update 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 card_id	string	Required	Card ID. Example: card123
Card Name name	string	Optional	Card Name
Description desc	string	Optional	Description
Move to List ID idList	string	Optional	Trello list ID — 24-char hex. Find via List Lists on a board.
Due Date due	string	Optional	Due Date. Example: 2025-06-30T17:00:00.000Z
Archive closed	options	Optional	Archive. Options: No, Yes

Sample request

{
  "card_id": "e.g. card123",
  "name": "{{trigger.name}}",
  "desc": "{{trigger.desc}}",
  "idList": "e.g. list456",
  "due": "e.g. 2025-06-30T17:00:00.000Z"
}

Returns

{
  "id": "card123",
  "name": "Updated card",
  "idList": "list456"
}

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

FAQ

Questions about Update Card.

What does the Update Card action do in Trello?

Updates a Trello card: name, description, list, due date, position, members, or labels. Only the fields you pass are changed.

What inputs does Update Card require?

Required: Card 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 Update Card support batch operations?

Yes. Run Update 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