Trello

Trello REST API (project management). 136 operations: cards (create, get, update, move, archive, delete) with their comments, attachments, labels, members, votes, stickers and custom field values; checklists and check items; lists (create, archive, move, bulk-move every card); boards with their lists, cards, labels, custom fields, actions, Power-Ups and membership; labels; custom field definitions and dropdown options; members and starred boards; workspaces and their membership; actions and emoji reactions; search across cards, boards and members; webhook management; and notifications.

Credential: Trello API key and token - see Credentials.

Token scopes

Each operation below lists the token scope it needs. Token scopes are chosen once, when the Trello token is authorized, and it cannot be widened afterwards. Trello has NO consent screen to revisit and NO per-endpoint permission table: a token carries some subset of exactly three scopes - read, write and account - fixed at the moment it is minted at trello.com/app-key along with a fixed lifetime (1 hour, 1 day, 30 days, or never). So the table below follows the one rule Trello does state: a read needs read, a write needs write, and anything reaching the authorizing member's OWN account - their email address, their profile, their notifications, their starred boards - needs account on top. Two things this catches people out on. First, because scope is baked into the token, a 401 is not something you fix by editing a setting: you generate a NEW token and replace the credential's key:token value. Second, a token that has expired reads exactly like one that was never granted the scope, and Trello's error body for both is the same plain-text invalid token. If a run fails with a permission error, the node names the missing token scope in the error - grant it and re-run; you do not need to rebuild the workflow.

Operations (136)

Cards

Card comments

Card attachments

Card labels & members

Card stickers

Card custom fields

Checklists

Checklist items

Lists

Boards

Board members

Labels

Custom fields

Members

Workspaces

Actions

Search

Webhooks

Notifications & token

Example

Tick a checklist item off from the card, not the checklist

A deploy workflow finishes and the release card's "Deploy to production" checklist item should tick itself. The obvious call — PUT the checklist, since that is where the item lives — does not exist in Trello's API at all: there is no update route under /1/checklists/{id}/checkItems. The ONLY way to change a check item is through the card that owns it (PUT /1/cards/{id}/checkItem/{idCheckItem}), which is why this operation asks for a card ID as well as the item ID. Getting that wrong is the single most common reason a Trello automation 404s.

Set Operation to updateCardCheckItem, then fill in:

Sets {{step.checkItem}} (the whole updated item, including state and pos), plus {{step.id}} and {{step.url}}. Trello returns a 400 with a plain-text body — not JSON — when an ID belongs to the wrong resource type, so "invalid id" here almost always means the checklist's ID was pasted into cardId.