Trello

Overview

The Trello nodes connect your workflows to Trello through its REST API v1. Use them to automate your board: create a card when an order comes in, move it across lists when a status changes, comment progress, or list a list’s cards to process them.

There are six nodes, one per operation:

Node	Operation	HTTP method
Trello: Create card (trelloCreateCard)	Create a card in a list	POST /cards
Trello: Get card (trelloGetCard)	Read a card by its id	GET /cards/{id}
Trello: Update card (trelloUpdateCard)	Update fields (incl. move/archive)	PUT /cards/{id}
Trello: Delete card (trelloDeleteCard)	Delete a card	DELETE /cards/{id}
Trello: Add comment (trelloAddComment)	Add a comment	POST /cards/{id}/actions/comments
Trello: List cards (trelloListCards)	List a list’s cards	GET /lists/{idList}/cards

Credential

The nodes use a Trello credential. Create it in Credentials → Add → Trello with these fields:

Field	Description
API key	Your Trello API key, from trello.com/app-key.
Token	The token generated when you authorize your API key (Token link on the same page). Never shown in logs.

Trello authentication uses key + token sent on every request. You can verify the credential with the Test button, which calls GET /members/me.

Important: ids and moving cards

• In Trello everything is referenced by id (24-character strings): the list (idList), the card, members. You can get a list id, for example, with the HTTP node over GET /boards/{idBoard}/lists, or from Trello’s URLs/shortcuts.
• To move a card across columns there’s no separate node: use Trello: Update card and include idList (the destination list id) in the fields JSON. To archive a card without deleting it, set {"closed": true}.

Nodes

Trello: Create card (trelloCreateCard)

Parameter	Type	Required	Description
credentials_id	credential	Yes	Trello credential
id_list	text	Yes	id of the list to create the card in
name	text	Yes	Card title
desc	text	No	Description
due	text	No	Due date ISO (e.g. 2026-08-15T10:00:00Z)
id_members	text	No	Member ids to assign, comma-separated
pos	text	No	Position: top, bottom or a number

Output: the created card, including its id and shortUrl.

Trello: Get card (trelloGetCard)

Parameter	Type	Required	Description
credentials_id	credential	Yes	Trello credential
card_id	text	Yes	Card id
fields	text	No	Comma-separated fields to return

Trello: Update card (trelloUpdateCard)

Parameter	Type	Required	Description
credentials_id	credential	Yes	Trello credential
card_id	text	Yes	Card id
fields	JSON	Yes	Fields to update, e.g. {"idList":"...","closed":true}

Trello: Delete card (trelloDeleteCard)

Parameter	Type	Required	Description
credentials_id	credential	Yes	Trello credential
card_id	text	Yes	id of the card to delete

Trello: Add comment (trelloAddComment)

Parameter	Type	Required	Description
credentials_id	credential	Yes	Trello credential
card_id	text	Yes	Card id
text	text	Yes	Comment text

Trello: List cards (trelloListCards)

Parameter	Type	Required	Description
credentials_id	credential	Yes	Trello credential
id_list	text	Yes	List id
limit	number	No	Max cards
fields	text	No	Comma-separated fields to return

Output: the array of cards in the list.

Example

Create a card from a form:

• Node: Trello: Create card
• id_list: 66ab12cd34ef56ab78cd90ef
• name: Order: {{data.customer}}
• desc: {{data.details}}

Output:

{
  "id": "66cd34ef56ab78cd90ef12ab",
  "name": "Order: ACME Inc.",
  "shortUrl": "https://trello.com/c/AbCdEfGh",
  "idList": "66ab12cd34ef56ab78cd90ef"
}

Error handling

Each node classifies errors so the engine knows whether a retry makes sense:

Situation	Retryable	What to do
Validation (400)	No	Trello returns the reason (e.g. invalid value for idList). Fix the data.
Not found (404)	No	The card or list doesn’t exist. Check the id.
Authentication (401/403)	No	Invalid key/token or no permission on the board. Check the credential.
Server (500)	Yes	Temporary Trello error; retried automatically.
Rate limit (429)	Yes	Trello’s Retry-After is honored and retried.
Network / Timeout	Yes	Transient issue; retried automatically.

Validation errors are not retried

Bad data is not retried: retrying with the same input would only repeat the failure. Fix the input and run again. You can see automatic retries in the Retry queue (DLQ) panel.

See also

• Jira (Atlassian) and Asana — other work-management integrations.
• Retry queue (DLQ) — how failed executions are retried.
• HTTP node — for Trello endpoints not covered by these nodes (boards, lists, labels…).