Can I create cards from multiple Slack channels?

Yes, but you need separate Zaps for each channel. Zapier's Slack trigger only monitors one channel per Zap.

What happens if someone edits a message after the card is created?

Nothing - Trello cards won't update automatically. You'd need a separate Zap with 'Message Updated' trigger to handle edits.

Can I assign the card to the person who posted the Slack message?

Only if that person's Slack username exactly matches their Trello username. Otherwise you need a lookup table or manual assignment.

How do I prevent cards from weekend or after-hours messages?

Add a Filter step that checks the message timestamp against business hours before creating the Trello card.

Beginner~8 min setupCommunication & Project ManagementVerified April 2026

How to Create Trello Cards from Slack Messages with Zapier

Automatically create Trello cards when team members use keywords or reactions in Slack channels.

Steps and UI details are based on platform versions at time of writing — check each platform for the latest interface.

Zapier

Also on:Make N8n Power-automate Pipedream

Best for

Teams that need to capture decisions and action items from Slack conversations without manual copy-paste work.

Not ideal for

High-volume channels that generate 100+ messages daily - you'll create too many cards and hit rate limits.

Sync type

real-time

Use case type

routing

Real-World Example

💡

A 12-person marketing team uses this to track campaign ideas shared in #marketing-brainstorm. When someone reacts with ⭐ to a message or types 'ACTION:', a Trello card is created in their Campaign Ideas board with the message content and author. Before automation, good ideas got buried in chat history and the team missed 60% of actionable suggestions.

What Will This Cost?

Drag the slider to your expected monthly volume.

Monthly workflow runs

/mo

505005K50K

Each platform counts differently — Zapier: 1 task per trigger. Make: 1 operation per module per record. n8n: 1 execution per run.

$30/mo if billed monthly

Pipedream

$29/mo

Basic plan

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.

Admin or member access to the Slack workspace where you want to monitor messages

Trello account with write access to the board where cards should be created

Zapier account with available task quota for the expected message volume

The Zapier app added to your target Slack channel (public channels auto-add, private need manual invite)

Field Mapping

Map these fields between your apps.

Field	API Name	Description
Required
Card Name		The title of the Trello card - make it descriptive with user context
Board		Target Trello board where cards will be created
List		Specific list within the board for new cards

4 optional fields▸ show

Card Description		Maps the full Slack message content including any formatting
Labels		Color-coded tags to categorize cards by channel or message type
Due Date		Optional deadline, useful for action items with time constraints
Position		Where to place new cards in the list (top, bottom, or specific position)

Step-by-Step Setup

Dashboard > Create Zap > Slack

Connect Slack to Zapier

Click 'Create Zap' from your Zapier dashboard. Search for 'Slack' in the trigger app selector and click it. Choose 'New Message Posted to Channel' as your trigger event - this fires every time someone posts in your target channel. Click 'Continue' to proceed to authentication.

1Click the orange 'Create Zap' button
2Type 'Slack' in the app search box
3Select 'New Message Posted to Channel' trigger
4Click 'Continue' button

✓ What you should see: You should see the Slack authentication screen asking for workspace permissions.

Slack > Authentication

Authenticate your Slack workspace

Click 'Sign in to Slack' and select your workspace from the dropdown. You'll be redirected to Slack's permission screen. Grant Zapier access to read messages and channel information. After approval, you'll return to Zapier with a green connection indicator.

1Click 'Sign in to Slack'
2Select your workspace from the list
3Click 'Allow' on the permission screen
4Wait for redirect back to Zapier

✓ What you should see: You should see your Slack workspace name with a green checkmark next to it.

⚠

Common mistake — If you don't see your target channel in the next step, the Zapier app needs to be added to that channel first.

Slack > Trigger Setup

Configure the Slack trigger

Select the channel where you want to monitor messages from the Channel dropdown. Choose 'Any' for Bot/User Messages to capture both human and bot posts. Leave Message Content filtering blank for now - we'll add keyword filtering in the next step. Set the trigger to fire on all new messages.

1Select your target channel from the dropdown
2Choose 'Any' for Bot/User Messages
3Leave Message Content field empty
4Click 'Continue'

✓ What you should see: Zapier will pull in a recent message from your selected channel as sample data.

⚠

Common mistake — Private channels won't appear unless you've manually added the Zapier bot to them in Slack first.

Zapier

click +

search apps

Slack

Configure the Slack trigger

Slack

module added

Slack > Test Trigger

Test the Slack trigger

Click 'Test trigger' to pull sample data from your channel. Zapier will show you the most recent message structure including user name, message text, timestamp, and channel info. This data preview helps you understand what fields you can map to Trello later. If no data appears, post a test message in your Slack channel.

1Click 'Test trigger' button
2Review the sample message data
3Check that user, text, and timestamp fields populated
4Click 'Continue with selected record'

✓ What you should see: You should see a sample message with fields like 'text', 'user', 'ts', and 'channel' populated with real data.

⚠

Common mistake — The user field shows internal Slack IDs, not display names - you'll need to map this correctly in Trello.

Zapier

▶ Turn on & test

executed

✓

Slack

✓

Trello

🔔 notification

received

Zap Steps > + > Filter

Add keyword filtering

Click the + icon to add a Filter step between Slack and Trello. This prevents every message from creating cards. Set up a condition like 'Text contains ACTION:' or check if the message has specific emoji reactions. Without filtering, you'll create hundreds of unwanted cards from normal chat.

1Click the + between trigger and action steps
2Select 'Filter by Zapier'
3Choose 'Text' field from Slack data
4Set condition to 'Contains' and enter your keyword

✓ What you should see: You should see a filter rule that only continues when your keyword condition is met.

⚠

Common mistake — Case sensitivity matters - 'ACTION:' and 'action:' are different. Use 'Text contains' with lowercase for broader matching.

Slack

trigger

filter

Condition

matches criteria?

yes — passes through

no — skipped

Trello

notified

Zap Steps > + > Trello

Connect Trello to Zapier

Add Trello as your action app by clicking the + button. Search for Trello and select 'Create Card' as the action event. This will prompt you to authenticate with your Trello account. Choose the Trello account that has access to your target board.

1Click + to add action step
2Search and select 'Trello'
3Choose 'Create Card' action
4Click 'Continue'

✓ What you should see: Zapier will show the Trello authentication popup asking for account access.

Trello > Authentication

Authenticate Trello

Click 'Sign in to Trello' and enter your Trello credentials. Grant Zapier permission to read your boards and create cards. After authentication, you'll see a list of your Trello boards. This connection allows Zapier to write new cards to any board you have access to.

1Click 'Sign in to Trello'
2Enter Trello email and password
3Click 'Allow' on permission screen
4Wait for redirect to Zapier

✓ What you should see: You should see your Trello account connected with a green checkmark.

⚠

Common mistake — Guest boards won't appear in the list - you need full member access to create cards via API.

Trello > Action Setup

Configure Trello card creation

Select your target board and list from the dropdowns. Map the Slack message text to the card description field. Set the card name to include the Slack user and timestamp for context. Add any default labels or due dates that make sense for your workflow. Leave members blank unless you want to auto-assign cards.

1Select Board from dropdown
2Choose List where cards should be created
3Map Slack 'Text' to Card Description
4Set Card Name with user and context

✓ What you should see: You should see your board and list selected with field mappings showing Slack data preview.

⚠

Common mistake — Don't map raw Slack user IDs to member fields - Trello won't recognize them and cards will fail to create.

Trello > Test Action

Test the complete workflow

Click 'Test action' to create a sample Trello card using your Slack message data. Check your Trello board to verify the card was created with correct title, description, and any labels you configured. The test uses the sample message from step 4, so don't worry if the content looks odd.

1Click 'Test action' button
2Wait for success confirmation
3Open your Trello board in new tab
4Verify the test card was created

✓ What you should see: You should see a new card in your Trello list with the Slack message content in the description.

⚠

Common mistake — Test cards count against any board limits you have set, so delete them after verification if needed.

Publish > Zap Name

Turn on the Zap

Name your Zap something descriptive like 'Marketing Slack to Campaign Ideas' and click 'Publish'. The automation is now live and will create Trello cards for new messages that match your filter criteria. Zapier will show you a success screen with options to create another Zap or view your dashboard.

1Enter descriptive name for your Zap
2Click 'Publish Zap'
3Confirm activation on popup
4Note the Zap URL for future edits

✓ What you should see: You should see a confirmation screen showing your Zap is now active and monitoring for new messages.

⚠

Common mistake — Published Zaps start monitoring immediately - post a test message with your keyword to verify everything works.

Going live

Production Checklist

Before you turn this on for real, confirm each item.

Test the keyword filter with various message formats your team actually uses

Set up Slack channel notifications so you know when cards are created

Create a naming convention for cards that includes channel context

Add error notification to a dedicated Slack channel for failed card creation

Document the trigger keywords so team members know how to create cards

Monitor task usage for the first week to avoid hitting Zapier plan limits

Troubleshooting

Common errors and how to fix them.

Frequently Asked Questions

Common questions about this workflow.

Analysis

VerdictWhy Zapier for this workflow

Use Zapier for this if your team uses simple keywords to mark important messages and you need cards created within 1-2 minutes. The webhook trigger is reliable and the filter step prevents spam cards from normal chat. Skip Zapier if you need complex message parsing or want to batch multiple messages into single cards - Make handles conditional logic better for those scenarios.

Cost

Real costs add up fast. Each message that matches your filter burns 1 task. A team posting 50 ACTION: messages per month hits 50 tasks, fitting easily in the free tier. But active channels can generate 200+ matches monthly, pushing you to the $20/month plan. Make handles the same volume for free up to 1,000 operations.

Tradeoffs

Make beats Zapier on complex filtering - you can check message patterns, user roles, and time conditions in one scenario instead of multiple filter steps. N8N gives you proper regex matching for sophisticated keyword detection. Power Automate integrates better if you're already using Teams instead of Slack. But Zapier wins on setup speed - the guided interface gets you running in 10 minutes versus 30+ on other platforms.

You'll hit three gotchas after going live. First, edited Slack messages don't update existing Trello cards, creating confusion when details change. Second, Slack user IDs don't match Trello usernames, so auto-assignment fails unless you build a lookup table. Third, busy channels will blow through your task quota - that marketing team might post 300 'ACTION:' messages monthly instead of the expected 50.

Ideas for what to build next

→
Add reaction triggers — Modify the trigger to fire on specific emoji reactions instead of keywords. This reduces noise and makes card creation more intentional.
→
Create priority routing — Use different Trello lists or boards based on message content or the user who posted. High-priority keywords go to urgent lists.
→
Add Slack notifications — Send a reply in the original Slack thread when a card is created, including a link to the new Trello card for easy access.