TRELLO n8n INTEGRATION: AUTOMATE TRELLO WITH N8N

The Update List action allows you to modify properties of an existing Trello list programmatically. This is essential for workflows that need to rename lists based on date ranges, archive lists when projects complete, or reposition lists dynamically.

Key parameters:

• List ID: A required text field where you provide the unique identifier of the Trello list you wish to modify. You can find this ID in the list's URL or retrieve it using the "Get Many Lists" action.
• Update Fields: An optional section where you define which properties to change. Click "Add Field" to reveal options like name, position, or closed/archived status.

Use cases:

• Automatically rename a "This Week" list to include the current date range every Monday
• Archive "Done" lists at the end of each sprint and create fresh ones
• Reposition lists based on priority scores calculated from card data

This action retrieves multiple lists from a specified Trello board, making it perfect for workflows that need to iterate through lists, generate reports, or validate list structures before performing other operations.

Key parameters:

• Board ID: An optional text field to specify which board's lists to retrieve. If you have a board selected elsewhere in your workflow, you can pass it dynamically.
• Return All: A toggle switch that, when enabled, fetches every list without limits. Useful for boards with many lists.
• Limit: When "Return All" is disabled, this number field (default: 20) caps how many lists are returned.
• Additional Fields: Optional filters to refine your query.

Use cases:

• Generate a weekly report of all lists and their card counts across project boards
• Check if specific lists exist before creating cards
• Sync list structures between Trello and project management databases

The Get Cards action retrieves all cards from a specific Trello list. This is one of the most frequently used actions for building reporting workflows, data synchronization, and batch operations on cards.

Key parameters:

• List ID: A required text field identifying the list from which to pull cards.
• Return All: Toggle to retrieve every card in the list regardless of quantity.
• Limit: Number field (default: 20) to cap results when Return All is disabled.
• Additional Fields: Optional parameters for filtering or including specific card properties.

Use cases:

• Export all cards from a "Completed" list to a Google Sheet for client reporting
• Count cards per list to identify bottlenecks in your workflow
• Batch update all cards in a list with new labels or due dates

Use this action to retrieve detailed information about a single Trello list. It's ideal when you need specific list metadata, want to verify a list exists, or need to fetch list properties for conditional logic in your workflow.

Key parameters:

• List ID: A required text field where you enter the unique identifier of the target list.
• Additional Fields: Optional parameters to include extra data in the response.

Use cases:

• Check if a list is archived before attempting to add cards
• Retrieve list metadata to display in notifications
• Validate list IDs before running batch operations

The Create List action adds a new list to a specified Trello board. This is essential for dynamic project management where lists need to be created programmatically—like weekly sprint lists, client-specific columns, or event-based boards.

Key parameters:

• Board ID: Required text field specifying where the new list will be created.
• Name: Required text field for the list's title (e.g., "Sprint 47" or "Client: Acme Corp").
• Additional Fields: Optional settings like initial position on the board.

Use cases:

• Automatically create weekly sprint lists every Monday with the date range in the name
• Generate client-specific lists when new customers are onboarded
• Create "Done" lists for each month for archival purposes

This action archives (or unarchives) a Trello list. Archiving keeps your boards clean without permanently deleting information, making it perfect for completed sprints, finished projects, or seasonal content.

Key parameters:

• List ID: Required text field with the unique identifier of the list to archive/unarchive.
• Archive: Toggle switch determining the action. On = archive the list; Off = unarchive (restore) the list.

Use cases:

• Automatically archive "Done" lists at the end of each month
• Restore archived lists when recurring projects restart
• Clean up boards by archiving inactive lists older than 90 days

Update the properties of an existing Trello label, including its name and color. This action is useful for maintaining consistent labeling systems across boards or adapting labels to new categorization schemes.

Key parameters:

• Label ID: Required text field for the unique identifier of the label to modify.
• Update Fields: Optional section where you specify new values. Click "Add Field" to change the label's name or color.

Use cases:

• Standardize label names across all boards in your organization
• Change label colors to match new brand guidelines
• Update priority labels based on quarterly goal changes

This action removes a specific label from a Trello card. It's essential for workflows that manage card status through labels, cleaning up completed items, or re-categorizing cards based on new criteria.

Key parameters:

• Card ID: Required field to identify the target card. Can be selected from a list or provided directly.
• Label ID: Required text field specifying which label to remove.

Use cases:

• Remove "Urgent" labels when cards move to "In Progress"
• Clean up client labels when projects are completed
• Strip outdated category labels during quarterly reviews

Retrieve multiple labels from a specified Trello board. This action is essential for building dynamic workflows that need to reference available labels, validate label configurations, or generate reports on label usage.

Key parameters:

• Board: Required dropdown to select the Trello board from which to retrieve labels.
• Additional Fields: Optional filters to refine the label query.

Use cases:

• Audit label usage across boards to identify unused labels
• Build dropdown menus in forms that pull live label options from Trello
• Sync label configurations between Trello and external databases

Retrieve detailed information about a single Trello label. Use this when you need specific label metadata for conditional logic, validation, or display purposes.

Key parameters:

• Label ID: Required text field with the unique identifier of the label to retrieve.

Use cases:

• Verify a label exists before attempting to add it to cards
• Fetch label color and name for formatted notifications
• Validate label IDs passed from external systems

This action deletes a Trello label permanently. Use with caution—once deleted, the label is removed from all cards that had it assigned.

Key parameters:

• Label ID: Required text field specifying the unique identifier of the label to delete.

Use cases:

• Clean up deprecated labels during board maintenance
• Remove duplicate labels created by error
• Eliminate outdated category labels during workflow restructuring

Create a new label on a Trello board. Labels are essential for categorizing and filtering cards, and this action allows you to create them programmatically for new projects, clients, or categories.

Key parameters:

• Board: Required dropdown to select where the label will be created.
• Name: Required text field for the label's title.
• Color: Optional dropdown to assign a color (null for colorless labels).

Use cases:

• Create client-specific labels when new customers are onboarded
• Generate project labels automatically when projects are created in your PM tool
• Add priority labels dynamically based on incoming request data

Add an existing label to a Trello card. This is one of the most commonly used actions for categorizing cards automatically based on form submissions, webhook data, or workflow conditions.

Key parameters:

• Card ID: Required field to identify the target card.
• Label ID: Required text field specifying which label to add.

Use cases:

• Auto-label cards based on form response categories
• Add "High Priority" labels to cards from VIP customers
• Tag cards with project labels based on webhook data

Modify an existing checklist item on a Trello card. This action is perfect for tracking progress, updating task names, or marking items complete/incomplete programmatically.

Key parameters:

• Card: Required dropdown to select the card containing the checklist.
• CheckItem ID: Required text field with the unique identifier of the checklist item.
• Additional Fields: Optional section for specifying new values (name, state, position).

Use cases:

• Mark checklist items complete when related tasks finish in other tools
• Update item names to include completion timestamps
• Reset checklist items to incomplete when cards are recycled

Retrieve multiple checklists from a Trello card. This action is essential for workflows that need to audit checklist completion, synchronize checklists with external systems, or generate task reports.

Key parameters:

• Card: Optional dropdown to specify which card's checklists to retrieve.
• Additional Fields: Optional parameters for filtering results.

Use cases:

• Generate completion reports showing checklist progress across cards
• Sync Trello checklists to project management databases
• Validate that required checklists exist before processing cards

Retrieve all completed checklist items from a specific checklist. This action is perfect for generating done-reports, calculating completion rates, or triggering follow-up actions when items are checked.

Key parameters:

• Additional Fields: Optional parameters to specify the checklist and filter results.

Use cases:

• Generate weekly "completed tasks" reports
• Calculate checklist completion percentages for dashboards
• Trigger notifications when all items in a checklist are complete

Retrieve all items from a Trello checklist, regardless of their completion state. This is essential for auditing checklists, syncing task lists, or building overview reports.

Key parameters:

• Card: Required dropdown to specify which card's checklists to access.
• CheckItem ID: Optional text field to target a specific item.
• Additional Fields: Optional filters and customization options.

Use cases:

• Export all checklist items to Google Sheets for comprehensive reporting
• Count total vs. completed items to calculate progress percentages
• Validate checklist contents match template requirements

Retrieve detailed information about a single Trello checklist. Use this when you need checklist metadata, want to verify existence, or need specific properties for conditional logic.

Key parameters:

• Checklist ID: Optional text field with the unique identifier of the checklist.
• Additional Fields: Optional parameters to customize the response.

Use cases:

• Verify a checklist exists before adding items
• Fetch checklist metadata for formatted reports
• Retrieve checklist positions for reordering operations

Remove a specific item from a Trello checklist. This action is useful for cleaning up completed or obsolete items, maintaining checklist accuracy, and automating item lifecycle management.

Key parameters:

• Card: Required dropdown to select the card containing the checklist.
• CheckItem ID: Required text field specifying which item to delete.

Use cases:

• Remove canceled tasks from active checklists
• Clean up test items after checklist validation
• Delete duplicate items created by sync errors

Delete an entire Trello checklist from a card. This is useful for removing obsolete checklists, cleaning up after project phases, or resetting cards for reuse.

Key parameters:

• Card: Required dropdown to identify the parent card.
• Checklist ID: Text field specifying which checklist to remove.

Use cases:

• Remove "Setup" checklists after cards move past onboarding
• Clean up draft checklists that weren't finalized
• Delete template checklists after items have been migrated

Add a new item to an existing Trello checklist. This is essential for dynamically building task lists, adding items from external sources, or populating checklists from templates.

Key parameters:

• Checklist ID: Required text field identifying the target checklist.
• Name: Required text field for the new item's title.
• Additional Fields: Optional settings like position and initial checked state.

Use cases:

• Add task items from form submissions to project checklists
• Populate checklists from template databases
• Create items for each line item in invoices or orders

Add a new checklist to a Trello card. This action is perfect for creating standardized task lists, adding process checklists to new cards, or building dynamic task structures.

Key parameters:

• Card: Required dropdown to specify which card gets the checklist.
• Name: Required text field for the checklist's title.
• Additional Fields: Optional settings for advanced configuration.

Use cases:

• Add onboarding checklists to new client cards automatically
• Create deployment checklists when cards move to "Ready for Launch"
• Generate QA checklists for content review cards

Modify an existing comment on a Trello card. This is useful for correcting automated comments, adding timestamps to updates, or appending information to existing notes.

Key parameters:

• Card: Required dropdown to identify the card with the comment.
• Comment ID: Required text field specifying which comment to update.
• Text: Required text field with the new comment content.

Use cases:

• Append status updates to automated notification comments
• Correct typos or errors in bot-generated comments
• Add resolution notes to initial support request comments

Remove a comment from a Trello card. Use this for cleaning up test comments, removing outdated information, or managing comment threads programmatically.

Key parameters:

• Card: Required dropdown to select the target card.
• Comment ID: Required text field specifying which comment to delete.

Use cases:

• Remove automated test comments after workflow validation
• Clean up duplicate comments created by sync errors
• Delete outdated status comments when cards are updated

Add a new comment to a Trello card. This is one of the most popular actions for keeping team members informed, logging automated actions, and maintaining audit trails.

Key parameters:

• Card: Required dropdown to specify which card receives the comment.
• Text: Required text field for the comment content.

Use cases:

• Log automated actions with timestamps for audit purposes
• Notify team members when external events affect cards
• Add summary notes when cards are created from external sources

Modify properties of an existing Trello card. This is one of the most versatile actions, allowing you to change names, descriptions, due dates, positions, and more.

Key parameters:

• Card: Required dropdown to identify which card to update.
• Update Fields: Optional section where you specify which properties to change and their new values.

Use cases:

• Update card names to include order numbers from external systems
• Set due dates based on SLA rules when cards enter support queues
• Move cards between lists based on status changes in other tools

Retrieve detailed information about a single Trello card. This action is essential for conditional logic, data synchronization, and building detailed reports.

Key parameters:

• Card: Required dropdown to specify which card to retrieve.
• Additional Fields: Optional parameters to customize which data is included.

Use cases:

• Check card status before performing conditional actions
• Fetch card details for formatted notifications
• Retrieve card data for synchronization with external databases

Permanently delete a Trello card. Use with caution—this action cannot be undone. Consider archiving cards instead unless permanent deletion is specifically required.

Key parameters:

• Card: Required dropdown to identify which card to delete.

Use cases:

• Delete test cards after workflow validation
• Remove spam cards created by unauthorized submissions
• Clean up duplicate cards created by sync errors

Create a new Trello card on a specified list. This is arguably the most-used action, perfect for turning form submissions, webhook events, or database entries into trackable cards.

Key parameters:

• List ID: Required text field specifying where the card will be created.
• Name: Required text field for the card's title.
• Description: Optional text field for detailed card content.
• Additional Fields: Optional settings for members, labels, due dates, and more.

Use cases:

• Create cards from Typeform or JotForm submissions
• Generate support tickets from customer emails
• Build cards from Slack messages using slash commands

Remove a member from a Trello board. This action is essential for managing team access, automating offboarding processes, and maintaining board security.

Key parameters:

• Board ID: Required text field identifying the target board.
• Member ID: Required text field specifying which member to remove.

Use cases:

• Automatically remove team members when they leave projects
• Clean up board access after project completion
• Revoke access when employees are offboarded from HR systems

Invite a new member to a Trello board via email. This action streamlines onboarding and makes it easy to add collaborators automatically.

Key parameters:

• Board ID: Required text field specifying the target board.
• Email: Required text field with the invitee's email address.
• Additional Fields: Optional settings for permission levels.

Use cases:

• Invite clients to project boards when deals close in CRM
• Add team members to boards when they're assigned in HR systems
• Onboard new employees to relevant boards automatically

Retrieve all members from a Trello board. This action is useful for auditing access, generating team reports, and validating member configurations.

Key parameters:

• Board ID: Required text field identifying the target board.
• Return All: Toggle to retrieve every member without limits.
• Limit: Number field (default: 20) when Return All is disabled.

Use cases:

• Audit board membership for compliance reporting
• Generate team rosters from project boards
• Sync Trello members with external user management systems

Add an existing Trello user to a board with a specified role. Unlike the invite action, this adds members who already have Trello accounts.

Key parameters:

• Board ID: Required text field specifying the target board.
• Member ID: Required text field with the Trello user's ID.
• Type: Dropdown to set membership level (Normal, Admin, Observer).
• Additional Fields: Optional settings for advanced configuration.

Use cases:

• Grant board access when team members are assigned in PM tools
• Automatically add admins to new boards based on department rules
• Restore member access after temporary project pauses

Modify properties of an existing Trello board. This allows you to change board names, descriptions, visibility settings, and more.

Key parameters:

• Board: Required dropdown to select which board to update.
• Update Fields: Optional section for specifying property changes.

Use cases:

• Update board names to include current quarter or year
• Change board visibility when projects move to different phases
• Modify board descriptions with updated project summaries

Retrieve detailed information about a single Trello board. This action is essential for validating board existence, fetching board metadata, and building conditional workflows.

Key parameters:

• Board: Required dropdown to specify which board to retrieve.
• Additional Fields: Optional parameters to customize the response.

Use cases:

• Verify boards exist before performing operations
• Fetch board metadata for reports and dashboards
• Retrieve board settings for configuration audits

Permanently delete a Trello board. This is an irreversible action—use with extreme caution and consider closing boards instead unless permanent deletion is required.

Key parameters:

• Board: Required dropdown to identify which board to delete.

Use cases:

• Clean up test boards after workflow development
• Remove duplicate boards created by errors
• Delete temporary project boards after data export

Create a new Trello board with specified properties. This action is perfect for automating project setup, creating client workspaces, or building structured board templates.

Key parameters:

• Name: Required text field for the board's title.
• Description: Optional text field for board details.
• Additional Fields: Optional settings for background, visibility, default lists, organization, permissions, and more.

Use cases:

• Create client project boards when deals close in CRM
• Generate sprint boards automatically each iteration
• Build event boards when conferences are scheduled

Retrieve multiple attachments from a Trello card. This action is useful for backing up attachments, syncing files to other storage systems, or generating attachment inventories.

Key parameters:

• Card ID: Required field to identify which card's attachments to retrieve.
• Additional Fields: Optional parameters to filter or customize results.

Use cases:

• Back up card attachments to Google Drive or Dropbox
• Generate attachment lists for compliance documentation
• Sync attachments with document management systems

Retrieve detailed information about a single Trello attachment. This is useful when you need specific attachment metadata or want to download a particular file.

Key parameters:

• Card ID: Required field identifying the parent card.
• Attachment ID: Required text field specifying which attachment to retrieve.
• Additional Fields: Optional parameters for customization.

Use cases:

• Fetch attachment URLs for inclusion in reports
• Verify attachment existence before processing
• Retrieve attachment metadata for file management workflows

Remove an attachment from a Trello card. Use this for cleaning up outdated files, removing incorrect uploads, or managing attachment lifecycles.

Key parameters:

• Card ID: Required field to identify the parent card.
• Attachment ID: Required text field specifying which attachment to delete.

Use cases:

• Remove outdated document versions when new ones are added
• Clean up test attachments after validation
• Delete sensitive files after they've been processed

Add an attachment to a Trello card from a URL. This action allows you to programmatically attach files, images, or documents from external sources.

Key parameters:

• Card ID: Required field specifying which card receives the attachment.
• Source URL: Required text field with the URL of the file to attach.
• Additional Fields: Optional settings for naming and customization.

Use cases:

• Attach generated reports or invoices to relevant cards
• Add screenshots from bug tracking tools to development cards
• Link reference documents when cards are created from forms