Skip to content
MoveWorkflows

Pipedream Trello steps in n8n

Updated 2026-10-21 · 3 min read · n8n: Trello (Native n8n node)

Trello workflows on Pipedream create cards from incoming requests and react when cards move between lists. n8n has a native Trello node with broad coverage and a webhook Trello Trigger; the trigger is model-based, so you filter events after it.

The n8n side

Trello node (n8n-nodes-base.trello):

Resource Operations
Attachment Create, Delete, Get, Get All
Board Create, Delete, Get, Update
Board Member Add, Get All, Invite, Remove
Card Create, Delete, Get, Update
Card Comment Create, Delete, Update
Checklist Create, Delete, Get, Get All, items: create, delete, update, get completed
Label Add to card, Create, Delete, Get, Get All, Remove from card, Update
List Archive/Unarchive, Create, Get, Get All, Get Cards, Update

Trello Trigger: registers a Trello webhook on a Model ID. Every action on that model arrives as an event.

What maps where

Pipedream (app trello) In n8n Status
Create Card Card → Create manual
Update Card Card → Update manual
Move Card to List Card → Update (List ID) manual
Add Comment Card Comment → Create manual
Add Checklist Checklist → Create manual
Add Attachment To Card Attachment → Create manual
Search Cards HTTP Request → /1/search manual
Archive Card Card → Update (Closed = true) manual
New Card (Instant) Trello Trigger on the board + If action.type = createCard manual
Card Moved (Instant) Trello Trigger + If updateCard with listBefore / listAfter manual
Card Updated, Card Archived, New Comment Added to Card (Instant) Trello Trigger + filter on action type and data manual

The converter has no Trello mapping yet: each step becomes a placeholder with its props (board, list, card IDs) in a comment, and the report lists the Trello credential.

Trello credentials in n8n

The Trello API credential takes an API key and a token:

  1. Open the Power-Up admin portal, create a Power-Up for your workspace.
  2. Generate the API key, then a token from the link next to it.
  3. Add your n8n base URL to the allowed origins.

Typical migration: card moved to Done

Pipedream: Trello Card Moved (Instant), list Done → Slack Send Message. n8n: Trello Trigger (Model ID = board ID) → If {{ $json.action.type }} = updateCard and {{ $json.action.data.listAfter.name }} = Done → Slack → Message → Send.

Trello migration pitfalls

  • Rate limits. 300 requests per 10 seconds per API key and 100 per 10 seconds per token; /1/members has its own limit of 100 per 900 seconds.
  • Webhook verification. Trello sends a HEAD request when the webhook is created; the n8n workflow must be active (production URL) or reachable in test mode.
  • Noise. A board-level trigger fires on every edit by every member. Filter early to save executions.
  • IDs vs names. Nodes need IDs; names change. Use the .json trick to get them once.

How to move your Trello workflows

  1. Export from Pipedream.
  2. Upload on /convert; the free report lists every Trello step with its props.
  3. Get the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

See the Pipedream to n8n guide. Related: Asana, monday.com, Jira.

FAQ

How does the Trello Trigger choose events?
It watches a Model ID (a board, list, card or member) and receives every action on it. There is no event picker; filter on action.type (createCard, updateCard, commentCard…) after the trigger.
Where do I find a board or list ID?
Add .json to a Trello board or card URL and read id or idList from the result. Pipedream props usually already contain these IDs.
What credential does n8n use for Trello?
An API key plus a token. Create a Power-Up in the Trello Power-Up admin portal, generate the key and token, and add your n8n base URL as an allowed origin.
Do Trello steps convert automatically?
No. They arrive as placeholders with their props (board, list, card name, description), and the report lists the Trello credential to create.

Related

Sources