Trello n8n integrationAutomate Trello with n8n.

Attaches a file to a card that already exists, by handing Trello the address where the file lives. It comes back with its own ID for the later steps.

• Card ID: the card that receives the file. Pick it from the list, or feed it with an expression, the n8n syntax that reuses a field of the incoming item, such as {{ $json.id }}.
• Source URL: the address of the file to add.
• Name and MIME Type (Additional Fields): the label shown on the card, and the content type such as image/png.

Detaches one file from a card. Trello needs both halves of the address: which card, and which attachment on that card.

• Card ID: the card the file is attached to.
• Attachment ID: the identifier of the attachment itself, usually captured when it was created or listed.

Fetches one attachment and returns its data, without touching the card around it.

• Card ID: the card holding the attachment.
• Attachment ID: the attachment to read.
• Fields (Additional Fields): either all or a comma separated list, when only two or three properties matter downstream.

Returns every attachment carried by one card, as one item per attachment, ready to loop over.

• Card ID: the card whose attachments are listed.
• Fields (Additional Fields): all, or the short list of properties to keep so the output stays readable.

Spins up a new Trello board and returns it. On its own the board is empty, unless the default lists or a source board are asked for.

• Name: the board name, the only required field.
• Description: the text shown in the board menu.
• Lists (Additional Fields): adds the default set of lists, To Do, Doing and Done. It is ignored when a source board is given.
• Source IDs and Keep From Source: copy an existing board, and pass cards to keep its cards.
• Organization ID and Permission Level: the team the board belongs to, and whether it stays private, org or public.

Removes a board for good. Nothing else is asked, so the workflow has to be sure of the board it points at, and an archive through Update a board is the reversible option when a trace still matters.

• Board: the board to delete, chosen from the list in the node or given by ID, often the one a previous step created.

Reads one board and returns its data, which is often what a workflow needs before it decides anything.

• Board: the board to read.
• Fields (Additional Fields): all, or a comma separated list among closed, dateLastActivity, desc, idOrganization, labelNames, name, prefs, shortUrl and the rest.
• Plugin Data: includes the data left by Power-Ups in the response.

Changes the properties of an existing board. Only the fields filled in Update Fields are sent, the rest stays as it is.

• Board: the board to edit.
• Closed: archives the board, the usual way to retire one without deleting it.
• Name and Description: the new name and the new description.
• Organization ID: moves the board to another team.
• Subscribed: whether the acting user follows the board.

Puts someone who already has a Trello account on a board, using their member ID, and sets what they are allowed to do.

• Board ID: the board that receives the member.
• Member ID: the identifier of the person to add.
• Type: normal, admin, or observer, which depends on the Trello plan.
• Allow Billable Guest (Additional Fields): lets organization admins add multi-board guests onto the board.

Lists the people attached to a board, one item per member.

• Board ID: the board to inspect.
• Return All: on, n8n pages through the API until every member is returned; off, Limit caps how many come back.

Sends a board invitation to an email address, which is the path to take when the person has no member ID yet.

• Board ID: the board to invite to.
• Email: the address the invitation goes to, in the form name@email.com.
• Type (Additional Fields): normal, admin or observer.
• Full Name (Additional Fields): the display name, at least one character, with no leading or trailing space.

Takes a member off a board. The Trello account survives untouched, only the access to that one board goes away, which makes this operation safe to run in a loop.

• Board ID: the board to remove the member from.
• Member ID: the person losing access, usually read from a previous listing rather than typed.

Creates a card in a given list and returns it with its ID, which is the value most of the following steps need.

• List ID: the list, that is the column, the card is created in.
• Name: the card title.
• Description: the body text of the card.
• Due Date and Position (Additional Fields): the deadline, and where the card sits, top, bottom or a positive float.
• Member IDs and Label IDs: comma separated lists, to assign and tag the card as it is born.

Erases a card and everything attached to it. Archiving with the Closed field of Update a card is the softer move when the history is worth keeping, so this operation is mostly for what should never have existed.

• Card: the card to delete, selected from the list in the node or given by ID.

Pulls one card and, when asked, the objects around it, which saves a second call to Trello.

• Card: the card to read.
• Fields (Additional Fields): all, or a list among desc, due, idList, idLabels, idMembers, name, shortUrl and the others.
• Members and Member Fields: return the member objects, then trim them to fullName, username, initials or avatarHash.
• Board, Custom Field Items, Stickers: include the board object, the custom field items, or the stickers.

Edits a card in place. List ID sits among these fields, so the operation that changes a detail also moves the card from one column to the next. For most teams, that move is the status change.

• Card: the card to edit.
• List ID: the list the card should sit in after the run.
• Due Date: the deadline on the card, with Due Complete next to it to say whether it was met.
• Label IDs: a comma separated list that replaces the labels on the card. Member IDs works the same way for people.
• Position: top, bottom or a positive float.
• Closed: archives the card.

Posts a comment under a card, which is the cheapest way to write what a workflow did where the team will actually read it.

• Card: the card the comment is attached to.
• Text: the body of the comment, often built from the fields of the incoming item.

Drops one comment from a card and leaves the card, its attachments and its other comments untouched. The comment is identified on its own, so the workflow needs the ID it kept when it posted.

• Card: the card the comment belongs to.
• Comment ID: the identifier of the comment to remove.

Rewrites the text of a comment that is already on a card, instead of adding another one under it.

• Card: the card carrying the comment.
• Comment ID: the comment being edited.
• Text: the new text, which replaces the previous one.

This operation attaches a new checklist to an existing Trello card and returns it with its own ID, the value every check item operation asks for afterwards.

• Card: the card that receives the checklist, picked from the dropdown or passed as an ID, often {{ $json.id }} coming from an earlier Trello step.
• Name: the title the checklist carries on the card.
• ID Of Checklist Source: optional, and it copies an existing checklist into the new one, so a standard set of steps arrives ready made.
• Position: top, bottom or a positive number.

A checklist stays empty until items land in it. This call adds one line and returns the check item, ID included.

• Checklist ID: the checklist that receives the line, usually the ID returned by Create a checklist.
• Name: the wording of the line as the team reads it on the card.
• Checked: switch it on and the line is created already ticked, handy when the step happened before the card existed.
• Position: top, bottom or a positive number.

The whole checklist leaves the card, every line with it. Trello wants the card here on top of the checklist, so an ID alone will not do.

• Card: the card holding the checklist.
• Checklist ID: the checklist to delete.

Here the checklist survives and one of its lines goes away. The nuance matters when a step stops being relevant instead of being done.

• Card: the card the checklist sits on.
• CheckItem ID: the line itself, not the checklist that holds it.

Sometimes a workflow only needs to look. The node returns the stored data of one checklist, which is enough to branch on before anything gets written back.

• Checklist ID: identifies the checklist to read.
• Fields: all, or a comma separated list of fields when the workflow needs one value and a lighter output.

The action name says items, the fields say otherwise: the call targets one CheckItem ID and returns that single line of a card checklist.

• Card: the card the line belongs to.
• CheckItem ID: the line to read.
• Fields: all or a comma separated list of fields.

This one returns the check items already ticked on a card, and it is the rare Trello operation with no required field in the node.

• Fields: all, or the short list limited to idCheckItem and state when a progress count is all the workflow needs.

Every checklist attached to the card comes back in one call, so a card can be inspected without knowing a single checklist ID in advance.

• Card: the card whose checklists are listed.
• Fields: all or a comma separated list of fields.

Ticking a box by hand is what this operation removes. It updates one line of a card checklist and returns it in its new state.

• Card: the card that carries the line.
• CheckItem ID: the line to update.
• State: complete or incomplete, the field that actually ticks or unticks the box.
• Name: rewrites the wording of the line, and Position moves it inside the checklist.

An existing board label gets pinned onto a card. The field expects the label ID, not its name and not its color, so fetch it first when only the wording is known.

• Card ID: the card to tag.
• Label ID: the label to add.

Labels live on a board, not on a card, and this operation creates one there with a name and a color.

• Board: the board the label is created on.
• Name: the wording of the label.
• Color: one of eleven values (black, blue, green, lime, null, orange, pink, purple, red, sky, yellow).

One field, one effect: the label named by its ID is deleted from the board. That ID usually comes from Get many labels, run a step earlier in the same workflow.

• Label ID: the label to delete.

Behind a label ID there is a name and a color, and this call returns them. It is what turns an opaque identifier into something a message can display.

• Label ID: the label to read.
• Fields: all or a comma separated list of fields.

Listing the labels defined on a board is where plenty of workflows start, because Add a label to a card and Remove a label from a card both want an ID that only this call hands over.

• Board: the board whose labels are listed.
• Fields: all or a comma separated list of fields.

The card loses the label, the board keeps it. That is the whole difference with Delete a label, which erases the label itself.

• Card ID: the card to untag.
• Label ID: the label to remove from it.

A label that already exists can change name, color, or both. Update Fields carries those two values.

• Label ID: the label to update.
• Name: the new wording.
• Color: the new color, taken from the same eleven values as Create a label.

One operation covers both directions: a list goes to the archive, or comes back to the board, depending on a single checkbox.

• List ID: the list to archive or to restore.
• Archive: checked, the list is archived; cleared, the list is unarchived.

A new column shows up on the board, at the position you pick.

• Board ID: the board the list is created in.
• Name: the name of the list, My list in the field placeholder.
• List Source: copies an existing list into the new one.
• Position: top, bottom or a positive float.

Single list, single call: the node returns the data stored for that list. Handy when a workflow holds the ID of a column and not its name.

• List ID: the list to read.
• Fields: all or a comma separated list of fields.

Every card sitting in one list comes back as items, one item per card, ready for a loop.

• List ID: the list to read the cards from.
• Return All: on, n8n walks the API pages until the last card of the column; off, Limit caps how many cards come back.
• Fields: all or a comma separated list of fields.

Board level this time: the call returns the lists of a board, which is how a workflow discovers the columns it can work with.

• Board ID: the board to read.
• Return All: on, every list comes back; off, Limit sets the maximum.
• Fields: all or a comma separated list of fields.

Renaming a column, moving it, closing it: all of that goes through Update Fields on one list.

• List ID: the list to update, picked from the node or fed through an expression such as {{ $json.id }}.
• Name: the new name of the list.
• Position: top, bottom or a positive float.
• Board ID: moves the list to another board.
• Closed: whether the list is closed, and Subscribed whether the acting user follows it.