Trello

Description

The Trello nodes connect your workflows to Trello through its REST API v1 (https://api.trello.com/1). Use them to automate a board: create a card when an order comes in, move it across lists when a status changes, post progress as a comment, or list a list’s cards to process them one by one.

There are six nodes, one per operation. All of them work on cards; boards, labels and lists themselves are not covered by these nodes (use the HTTP node for those endpoints).

Operations

Create card Create a card in a list.

Get card Read a card by its id.

Update card Update fields, move to another list, archive.

List cards List every card in a list.

Delete card Permanently delete a card.

Add comment Post a comment on a card.

Configuration

Node	Internal name	Endpoint used
Trello: Create card	`trelloCreateCard`	`POST /cards`
Trello: Get card	`trelloGetCard`	`GET /cards/{id}`
Trello: Update card	`trelloUpdateCard`	`PUT /cards/{id}`
Trello: List cards	`trelloListCards`	`GET /lists/{idList}/cards`
Trello: Delete card	`trelloDeleteCard`	`DELETE /cards/{id}`
Trello: Add comment	`trelloAddComment`	`POST /cards/{id}/actions/comments`

Every node takes a credentials_id field plus the parameters of its own operation. The exact table for each one is on its page.

Credentials

Service type: trello. Create it in Credentials → Add → Trello.

Field	Type	Required	Description
`api_key`	text	Yes	Your Trello API key, from trello.com/app-key (Power-Up admin).
`token`	password	Yes	Token generated when you authorize that API key (the Token link on the same page). Never shown in logs.

Trello authenticates with key + token sent as query parameters on every request — there is no OAuth flow and no bearer header. The Test button verifies the credential against GET /members/me.

Ids: where to get them

In Trello everything is referenced by id — 24-character hexadecimal strings — not by name:

List id (idList): needed to create or list cards. Get it with the HTTP node over GET /boards/{idBoard}/lists, or by appending .json to a board URL in your browser.
Card id: returned by Create card and by List cards, in the id field.
Member ids: needed to assign a card. GET /boards/{idBoard}/members returns them.

Moving and archiving cards

There is no separate “move card” node. Moving is an update:

To move a card to another column, use Update card with {"idList": "<destination list id>"}.
To archive a card without destroying it, use Update card with {"closed": true}.
Delete card is permanent and cannot be undone.

Output

Every node returns the Trello response as-is in data (Trello sends flat JSON, with no envelope), plus a _meta block with the module version, the affected id and the elapsed time.

{
  "data": {
    "id": "66cd34ef56ab78cd90ef12ab",
    "name": "Order: ACME Inc.",
    "shortUrl": "https://trello.com/c/AbCdEfGh",
    "idList": "66ab12cd34ef56ab78cd90ef",
    "closed": false
  },
  "_meta": {
    "moduleVersion": "1.0.0",
    "success": true,
    "id": "66cd34ef56ab78cd90ef12ab",
    "url": "https://trello.com/c/AbCdEfGh",
    "totalMs": 412
  }
}

API Used

Trello REST API v1 — https://developer.atlassian.com/cloud/trello/rest/

Error handling

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

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

Notes

Request timeout: 20 seconds. Retryable failures are retried up to 3 times with exponential backoff.
The token is never written to the logs — only a masked fragment (abcd…wxyz).
Dynamic variables ({{data.field}}) are resolved in the text fields of each node. The JSON field of Update card is not processed: put literal values there, or build the JSON in a previous node.