

How to Auto-Post Trello Updates to Slack with Zapier
Automatically send Slack messages when Trello cards move between lists or receive new comments.
Steps and UI details are based on platform versions at time of writing — check each platform for the latest interface.
Best for
Teams who need instant Slack notifications when project status changes in Trello without checking boards manually.
Not ideal for
Teams wanting digest summaries or complex conditional logic based on multiple card properties.
Sync type
real-timeUse case type
notificationReal-World Example
A 12-person marketing agency uses this to notify #client-projects whenever cards move from 'In Progress' to 'Review' on their campaign boards. Before automation, project managers checked 8 different Trello boards twice daily and clients waited hours for status updates.
What Will This Cost?
Drag the slider to your expected monthly volume.
Each platform counts differently — Zapier: 1 task per trigger. Make: 1 operation per module per record. n8n: 1 execution per run.





Prices shown for annual billing. Based on published pricing as of April 2026.
Estimated ROI
1000
min saved/mo
$583
labor value/mo
Free
no platform cost
Based on ~2 min manual effort per operation at $35/hr fully loaded labor cost.
Implementation
Before You Start
Make sure you have everything ready.
Field Mapping
Map these fields between your apps.
| Field | API Name | |
|---|---|---|
| Required | ||
| Card Name | ||
| Member Full Name | ||
| To List Name | ||
5 optional fields▸ show
| From List Name | |
| Board Name | |
| Card Description | |
| Due Date | |
| Card URL |
Step-by-Step Setup
Dashboard > Create Zap > Trello
Create New Zap with Trello Trigger
Click 'Create Zap' from your Zapier dashboard. Search for 'Trello' in the trigger app selector and select it. Choose 'Card Moved' as your trigger event since this captures list changes in real-time. This trigger fires instantly when any card changes position between lists on your selected board.
- 1Click the orange 'Create Zap' button
- 2Type 'Trello' in the app search box
- 3Select 'Trello' from the results
- 4Choose 'Card Moved' from the trigger events list
Trigger > Account > Sign in to Trello
Connect Your Trello Account
Click 'Sign in to Trello' and authorize Zapier access to your boards. You'll be redirected to Trello's authorization page where you must click 'Allow' to grant read permissions. Zapier needs board access to detect card movements and pull card details like names, descriptions, and member assignments.
- 1Click 'Sign in to Trello' button
- 2Enter your Trello email and password
- 3Click 'Allow' on the permission screen
- 4Wait for the green 'Connected' confirmation
Trigger > Board > To List
Select Board and Lists to Monitor
Choose the specific Trello board you want to monitor from the dropdown. Then select which destination lists should trigger notifications - typically 'Done', 'Review', or 'Completed' lists where status updates matter most. You can pick multiple lists, and Zapier will trigger when cards move TO any of these lists from anywhere else.
- 1Select your target board from the 'Board' dropdown
- 2Choose destination lists in the 'To List' field
- 3Leave 'From List' blank to catch moves from any list
- 4Click 'Continue' to proceed
Trigger > Test > Retest trigger
Test Trello Trigger
Zapier will search for recent card movements on your selected board. If no recent moves exist, manually move a test card to one of your monitored lists in Trello, then click 'Retest trigger'. The test should pull in card details like name, description, due date, and the member who moved it.
- 1Click 'Test trigger' to find existing data
- 2If no data found, move a card in Trello
- 3Return to Zapier and click 'Retest trigger'
- 4Verify the card data looks correct
Action > Slack > Send Channel Message
Add Slack Action Step
Click the '+' button to add an action step. Search for 'Slack' and select it as your action app. Choose 'Send Channel Message' as the action event - this posts public messages that all channel members can see. Private messages would use 'Send Direct Message' instead, but broadcasting requires channel visibility.
- 1Click the '+' button below the trigger
- 2Search for 'Slack' in the app selector
- 3Select 'Slack' from the results
- 4Choose 'Send Channel Message' action
Action > Account > Sign in to Slack
Connect Slack Workspace
Click 'Sign in to Slack' and select your target workspace from the list. You'll need to authorize Zapier to post messages on your behalf. Make sure you're connecting to the workspace that contains your project channels, not a personal or testing workspace. Zapier will request 'channels:read' and 'chat:write' permissions.
- 1Click 'Sign in to Slack' button
- 2Choose your workspace from the list
- 3Click 'Allow' to grant posting permissions
- 4Confirm your workspace name appears
Action > Channel > Message Text
Configure Channel and Message
Select the Slack channel where updates should be posted - this could be #general, #projects, or a client-specific channel. In the 'Message Text' field, build a notification using Trello card data from step 4. Include the card name, who moved it, and which list it moved to for complete context.
- 1Choose your target channel from the dropdown
- 2Click in the 'Message Text' field
- 3Insert Trello data: card name, member name, list names
- 4Add context text like 'moved to' between data fields
📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}Action > Test step
Test Slack Message
Click 'Test step' to send a real message to your selected Slack channel using the sample Trello data. Check your Slack channel to verify the message appears correctly with proper formatting and complete information. The test message will show actual card details from your earlier trigger test, not placeholder text.
- 1Click 'Test step' button
- 2Wait for 'Test successful' confirmation
- 3Switch to Slack and check your channel
- 4Verify message content and formatting
📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}Publish > Name > Publish
Name and Activate Zap
Give your Zap a descriptive name like 'Trello Project Updates to #client-work' so you can identify it later. Click 'Publish' to activate the automation. Once published, the Zap monitors your Trello board continuously and posts to Slack within 1-2 minutes of any card movements to your selected lists.
- 1Click 'Publish' in the top right
- 2Enter a descriptive Zap name
- 3Review the trigger and action summary
- 4Click 'Publish Zap' to activate
Going live
Production Checklist
Before you turn this on for real, confirm each item.
Troubleshooting
Common errors and how to fix them.
Frequently Asked Questions
Common questions about this workflow.
Analysis
Use Zapier for this if your team already lives in Slack and needs instant project visibility without Trello training. Setup takes under 10 minutes and works reliably for teams posting 50-200 status updates monthly. The guided interface makes it simple for non-technical project managers to configure. Skip Zapier if you need complex conditional logic or digest-style summaries - Make handles those scenarios better with branching workflows.
Real math: each card movement costs 1 Zapier task. A 10-person team moving 150 cards monthly through 'Review' and 'Complete' lists hits 150 tasks. That's $0 on Zapier's free tier until you hit 100 tasks, then $20/month for the Starter plan. Make charges $9/month for 1,000 operations, making it 55% cheaper for active boards.
Make beats Zapier with conditional routing - you can send different messages to different channels based on card labels or due dates in a single scenario. n8n offers free self-hosting but requires server management your team probably doesn't want. Power Automate integrates better if you're already using Microsoft Teams instead of Slack. Pipedream gives you custom JavaScript for complex message formatting. But Zapier wins on reliability - their Trello webhook integration rarely fails, while Make occasionally misses rapid card movements.
Things you'll hit: Trello's webhook sometimes stops firing after board permission changes, requiring you to reconnect the account. Cards moved by automation tools or integrations (not humans) may not trigger consistently. Free Slack workspaces limit message history, so important status updates disappear after 90 days. High-activity boards with 20+ daily movements will flood channels fast - start with filtering specific lists only.
Ideas for what to build next
- →Add Comment Notifications — Create a second Zap using 'New Comment on Card' trigger to broadcast when team members add important updates or questions.
- →Filter by Card Labels — Add Zapier Filter steps to only notify for cards with specific labels like 'Client Facing' or 'Urgent' to reduce notification noise.
- →Create Status Digest — Build a scheduled Zap that sends weekly summaries of all completed cards to stakeholder channels for reporting purposes.
Related guides
How to Share Notion Meeting Notes to Slack with Pipedream
~15 min setup
How to Share Notion Meeting Notes to Slack with Power Automate
~15 min setup
How to Share Notion Meeting Notes to Slack with n8n
~20 min setup
How to Send Notion Meeting Notes to Slack with Zapier
~8 min setup
How to Share Notion Meeting Notes to Slack with Make
~12 min setup
How to Create Notion Tasks from Slack with Pipedream
~15 min setup