Trello Card Movement Notifications to Slack - n8n Workflow

Project Managers who need instant updates on task progression.
Development teams utilizing Trello for agile sprint tracking.
Users seeking to bridge Trello actions with Slack communication using a powerful n8n workflow.
Anyone interested in leveraging n8n templates for event-driven alerts.

Keeping teams informed about project progress is critical. This specialized n8n workflow template addresses the communication gap between task management (Trello) and internal messaging (Slack). By utilizing a Trello webhook as the primary n8n trigger, the automation listens for specific card movement events on a chosen board. When a move occurs, the n8n node structure parses the event data, extracting the card's name, its previous location, and its new destination. This valuable information is then structured into a clear, readable message and instantly pushed via the Slack n8n node. Implementing this reliable n8n workflow eliminates the need for manual status checks and ensures real-time accountability across the team.

This efficient n8n workflow executes immediately when a defined event takes place in Trello. It follows three primary steps:

1. Trello Event Capture (Trello Trigger n8n node): The workflow begins when a Trello card is moved between lists on the configured board. This Trello n8n trigger acts as a webhook listener, catching the specific listAfter and listBefore data.


2. Data Structuring (Edit Fields n8n node): A Set n8n node processes the incoming JSON data. It extracts and defines custom variables: Task (Card Name), Previous Step (the list it left), and New Step (the list it entered). This preparation is crucial for crafting a clean message in the final step of this n8n workflow.


3. Notification Delivery (Slack n8n node): The final step uses the Slack n8n node to construct and send the alert. It uses the variables defined in the previous n8n node to generate a dynamic message (e.g., "Task: [Card Name] moved from [Previous List] to [New List]") to a specified user ID or channel, completing the execution of the n8n template.

To deploy and run this robust n8n workflow, follow these steps:

1. Importing the n8n Workflow Template: Copy the provided JSON code and import it directly into your n8n instance via the 'New' > 'Import from JSON' option.


2. Trello Credential Setup: You must configure a Trello API credential. Obtain your API key from the Trello App Key page and generate a Token from the same location. Paste both the key and the token into a new Trello API credential within your n8n setup.


3. Configuring the Trello Trigger: Select your new Trello credential in the Trello n8n trigger node. Crucially, replace the placeholder Model ID with the specific ID of the Trello board you want to monitor. Activate the n8n trigger webhook.


4. Slack Credential Setup: Create a new Slack OAuth2 API credential in n8n. This requires setting up a Slack application, granting necessary scopes (like chat:write and users:read), and obtaining the Bot User OAuth Token.


5. Configuring the Slack n8n node: Select your Slack OAuth2 credential. Update the User or Channel selection within the Slack n8n node to ensure the notification is delivered to the correct recipient in your workspace. Test the entire n8n workflow using the 'Execute Workflow' button to verify all connections.

Trello Trigger: This n8n trigger is the starting point, initiating the n8n workflow via a webhook whenever a card move event is detected on the linked Trello board. Key configuration involves setting the Trello Board ID.
Edit Fields (Set n8n node): A data manipulation n8n node. It extracts nested values from the Trello payload—specifically the names of the card, the list before the move (listBefore), and the list after the move (listAfter). These are defined as accessible variables for the subsequent n8n node.

• Send a message2 (Slack n8n node): The primary action n8n node. It utilizes the extracted variables to dynamically compose a status update message. Configuration targets a specific Slack user or channel using OAuth2 authentication.