Skip to main content

Trello

Read and write Trello boards - browse boards, lists and cards, search with Trello's operators, create, update, move, archive and delete cards, and work their comment threads.

Connect a Trello account with an API key and member token to run its boards end to end: list the boards the member belongs to, read a board's lists and label palette, window through a board's or a list's cards, search across everything they can see, create cards with members, labels and dates, move them between lists and positions, archive them reversibly or delete them permanently, and read and post card comments. Everything written through this connection is attributed in Trello to the member who authorised the token.

Connect

Credential fieldRequiredWhere it comes from
API key (API_KEY)YesFrom the Power-Up's page at trello.com/power-ups/admin. It identifies the Power-Up and is useless without a token minted for it.
Member token (TOKEN)YesGenerated and authorised from that same API key's page. It carries the full board access of the member who authorised it - there are no scopes to narrow it - and every write is attributed to them.

Tools

ToolAccessWhat it does
Whoami (yekar.trello.whoami)ReadThe Trello member this connection's token belongs to. Run it first - every other tool is scoped to this person's own boards, and Trello's permission errors arrive with the same status as a bad token.
List boards (yekar.trello.list-boards)ReadEvery board this connection's member belongs to. Archived boards are hidden unless you ask for them. Board ids (or their shortLinks) are what List lists and Search take.
Get board (yekar.trello.get-board)ReadOne board in full, including the names its owner gave each label colour - which is the only place to learn what a card's unnamed coloured label actually means on this board.
List lists (yekar.trello.list-lists)ReadThe lists (columns) of a board, in board order. Their ids are what Create card and Update card need - Trello accepts a list only by id, never by name.
List cards (yekar.trello.list-cards)ReadA window of cards from one board or one list, newest first. Trello has no cursor paging and reports no total - this returns at most limit cards and says when there may be more; use before to walk further back.
Get card (yekar.trello.get-card)ReadOne card in full - its description, list, members, labels, due date, and Trello's own counts of its comments, attachments and checklist items.
Search (yekar.trello.search)ReadSearch cards and boards across everything this token's member can see, using Trello's query operators (board:, member:, label:, is:open…). Results are relevance-ranked and capped - use List cards when completeness matters.
Create card (yekar.trello.create-card)WriteCreate a card in a list. Trello has no dry run: the card exists as soon as this returns, and every member watching the board is notified.
Update card (yekar.trello.update-card)WriteChange a card - rename it, rewrite its description, move it to another list or position, set or clear its dates, or replace its members and labels. Archiving and deleting are separate tools. Member and label lists REPLACE what is there.
Archive card (yekar.trello.archive-card)WriteArchive a card (or restore an archived one). This is the REVERSIBLE operation - the card leaves the board's lists but keeps its history, comments and id, and setting archived to false brings it back. Use this, not Delete card, unless the card must be destroyed.
Delete card (yekar.trello.delete-card)WritePERMANENTLY delete a card. Trello has no trash and nothing can undo this - the card, its comments, attachments and checklists are destroyed. Archive card is the reversible operation and is almost always what is wanted instead.
List card comments (yekar.trello.list-card-comments)ReadA window of the comments on a card, newest first. Trello reports no total - Get card carries its own comment count - so use before to walk further back through a long thread.
Add card comment (yekar.trello.add-card-comment)WritePost a comment on a card, attributed to the member whose token this connection holds. Everyone watching the card is notified immediately, and an @mention notifies that member - there is no draft state and no unsend.

Notes

  • Create a Power-Up at trello.com/power-ups/admin to get an API key, then generate a token from that Power-Up's API key page and authorise it. Paste BOTH here - a token is minted for one specific key and is useless with any other.
  • The token IS that member: it carries exactly their board access, and every card, move and comment made through this connection appears in Trello under their name. Bind automations using this integration as service connections so the attribution is a role rather than an individual's side effect.
  • Choose the token's expiry when you generate it. A token set to expire will stop this connection dead on that date with an authentication error, so either pick 'never' or plan the rotation.
  • Trello identifies everything by a 24-character id. Board and card ids can also be given as the 8-character code from a trello.com/b/… or /c/… URL, but a LIST is only ever addressed by its full id - see List lists.
  • Archiving and deleting are different: archiving is reversible and is what Trello's own Archive button does, while Delete card destroys the card, its comments and its attachments with no trash and no restore. They are separate tools here for that reason.
  • Trello reports no totals and has no cursor paging, so every listing is a window: it returns at most the limit asked for and says when there may be more. Counting a board's cards is not something this API can do.
  • Rate limits are two separate windows - 300 requests per 10 seconds per API key and 100 per 10 seconds per token - and the token's is the tighter one.
  • Add one credential per key/token pair - a production and a sandbox pair can live on the same connection.