Connecting Trello to n8n: automating cards, lists and boards (complete guide)

A well-maintained Trello board gives a clear view of a team's progress, but it stays a passive object: someone still has to open each new card, set a priority, move it to the right list, or chase a ticket that's sat without movement for too long. Connecting Trello to n8n changes that dynamic: every event (card created, moved, commented) can trigger a workflow that classifies, notifies or synchronizes automatically — including with a language model for decisions that need judgment rather than a fixed rule. This guide covers authentication, Trello's data hierarchy, the node and trigger, and two concrete examples, including AI-driven card qualification.

A study by Dag I. K. Sjøberg, An empirical study of WIP in kanban teams, published in 2018 in the proceedings of the 12th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM), analyzed more than 8,000 work items processed over four years by five teams working in Kanban. The main finding: lower work-in-progress (WIP) consistently shortens processing lead times, even though its effect on raw productivity is harder to isolate. Automating the triage and prioritization of incoming Trello cards, before they pile up in an already-crowded "To do" list, directly supports that result: fewer cards in simultaneous progress, shorter lead times for the ones that move forward.

When to automate Trello with n8n

Three use cases come up most often:

• Automatic qualification and prioritization: every card created (by a client through a form, an email turned into a ticket, or a team member) gets reviewed by a language model that assigns it a label, a priority or a destination list, before a human ever opens it.
• Targeted notifications on card movement: rather than relying on Trello's native notifications (often lost in the activity feed), n8n filters on the transitions that actually matter — a card moving to "Blocked," a card sitting in "In progress" with no update for several days — and alerts on Slack or by email only in those cases.
• Synchronization with external tools: a Trello card created from a form, a CRM, or a Slack conversation, or conversely cards pushed to a Google Sheets dashboard or a Supabase database for progress reporting.

If your team tracks tasks with finer-grained statuses and custom fields, our guide to connecting ClickUp to n8n will sometimes fit better; Trello remains preferable for simple visual boards that are quick to adopt for a team or external clients.

Authentication: API key and token, or OAuth1

Trello offers two authentication methods, and n8n supports both:

1. API Key + Token (the simplest for internal use): from the Trello developer page, generate an API key, then an authorization token tied to your account. In n8n, Credentials → New → Trello API, paste both values. All workflow actions then run with your own Trello permissions.
2. OAuth1: needed if the workflow must act on behalf of several distinct users rather than a single technical account — n8n handles the OAuth1 key exchange required by Trello's API, older on this point than most modern OAuth2 APIs.

For a typical team workflow (qualification, notifications, synchronization), the API key and token are enough and avoid the complexity of the OAuth1 flow. Reserve OAuth1 for integrations distributed across several Trello accounts.

Understanding Trello's hierarchy before configuring the node

Trello organizes data across three levels, simpler than ClickUp's or Notion's: Board (the visual workspace) → List (a column on the board, usually a status) → Card (the unit of work itself). A card always belongs to a List, and can be moved from one list to another — that move is in fact the status signal most automations rely on.

In n8n's Trello node, once the credential is connected, Board and List IDs can be picked from dropdown menus or pasted directly from the board's URL — no need to handle raw Trello identifiers for everyday use.

The Trello node's operations

The Trello node covers several resources:

Board resource: Create, Get, Update, Delete — managing the board itself, rarely used outside an automated initial setup.

Card resource: Create (title, description, destination list, due date), Get, Update (move to another list, change the description, add a due date), Delete.

List resource: Create, Get, GetAll, GetCards (retrieves every card in a given list — the basis for a digest or a grouped follow-up), Archive, Update.

Checklist resource: Create, Get, GetAll, Delete, plus fine-grained item management (CreateCheckItem, UpdateCheckItem, DeleteCheckItem, CompletedCheckItems) — useful for automatically breaking down a complex card into sub-steps generated by an LLM.

Label resource: Create, Get, GetAll, Update, Delete, plus AddLabel and RemoveLabel to apply or remove a label on a card — the most direct mechanism for an AI agent to visually mark a category or priority.

Card Comment resource: Create, Update, Delete — useful for an AI agent to log its reasoning directly on the card rather than in a separate channel.

Attachment and Board Member resources round out the node for linking files or managing assignments.

The Trello Trigger: a webhook that receives everything, filtered by you

n8n's Trello Trigger registers a real webhook on Trello's side: as soon as an event happens within the subscribed scope, Trello notifies the n8n workflow's URL in near real time. Configuration requires a single key parameter, the Model ID — the identifier of the Board, List or Card to watch.

An important difference from the ClickUp Trigger described in our ClickUp connection guide: the Trello Trigger has no native event-type filter in its configuration. It forwards every event within the subscribed scope — card creation, move, comment, member added, label changed — as an action object whose type field (createCard, updateCard, commentCard, addMemberToCard…) indicates the nature of the event. You therefore need an IF or Switch node right after the trigger to keep only the relevant action types, following the same logic detailed in our guide to the IF node and conditional routing.

One decision to make when setting the Model ID: subscribing to an entire Board's ID receives every event from all of its lists (the most common choice), while subscribing to a specific List's ID restricts the webhook to that single column — useful for watching only the "Incoming requests" list of a large board shared across teams, without having to filter out the other columns' moves.

Concrete example 1: AI qualification of incoming cards

A representative pipeline for a support or product team receiving requests from mixed sources:

1. Trello Trigger subscribes to the "Customer requests" Board, receiving every event from the board.
2. An IF node filters on {{$json.action.type === "createCard"}} to keep only card creations and ignore moves, comments or label changes.
3. An AI Agent node (see our complete AI Agent node guide) receives the card's title and description, and determines a category (bug, feature, question), a priority and the appropriate destination list, based on a prompt describing your team's criteria.
4. The Trello node (Card → Update operation) moves the card to the right list, applies a Label matching the priority, and adds a Comment briefly explaining the model's reasoning — so a human can verify and correct without guessing why that classification was chosen.
5. If the priority is "urgent," a Slack node immediately notifies the relevant team channel (see our guide to building an AI-powered Slack bot to build that notification).

This AI classification pattern follows the same logic as the email triage in the Inbox IA Pack (€79), applied here to board cards instead of incoming messages.

Concrete example 2: alerting on blocked cards

1. A Schedule Trigger (see our Schedule Trigger node guide) runs every weekday morning.
2. The Trello node (List → GetCards operation) retrieves cards from the "In progress" list whose dateLastActivity field, returned by the API, hasn't changed in more than 3 business days.
3. A Code node filters these cards and groups them by assigned member.
4. A Slack node sends a message grouped by assignee, with a direct link to each card, rather than a scattered notification per individual card.
5. Optional: an AI Agent drafts a summary of the blocker from the card's latest comments, so the Slack message gives context without having to reopen Trello.

A rate limit worth knowing

Trello's API enforces a limit of 300 requests per 10 seconds per API key and 100 requests per 10 seconds per token — the more constraining limit to watch in practice. Exceeding it returns a 429 status code. On a workflow that loops over a large number of cards (a full board sync, for example), process in batches with Split In Batches or add a short Wait between calls — the same precaution detailed in our article on pagination with the HTTP Request node. Using the Trello Trigger instead of regular polling avoids most of these calls in the first place: Trello pushes the event, n8n doesn't need to poll the API periodically.

In summary

The API key and token are enough for most team workflows, the Board/List/Card hierarchy is simpler to navigate than ClickUp's or Notion's, and the Trello Trigger has the advantage of being a real webhook — provided you filter the action.type field yourself, since no native per-event filter exists in its configuration. The Model ID (whole Board or specific List) and the 100-requests-per-10-seconds-per-token limit are the two details not to miss when setting up your first workflows. For an AI qualification pipeline already assembled, with classification prompts and routing logic ready to use, the Inbox IA Pack (€79) offers a starting point directly adaptable to a Trello card flow instead of an email inbox.