Short answer: Drop the "Trello → Update List" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
List ID listId | string | Required | List ID |
New Name name | string | Optional | New Name. Example: Done |
Archived closed | boolean | Optional | Archive this list |
{"listId": "{{trigger.listId}}","name": "e.g. Done","closed": "{{trigger.closed}}"}
{"id": "list123","name": "Done"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.