

How to Process Bug Reports from Slack to Trello with Make
Automatically convert Slack messages containing bug reports or feature requests into labeled Trello cards with proper assignments and due dates.
Steps and UI details are based on platform versions at time of writing — check each platform for the latest interface.
Best for
Product and development teams that use Slack for communication but need structured tracking in Trello
Not ideal for
Teams that prefer manual triage or use dedicated bug tracking tools like Jira
Sync type
real-timeUse case type
routingReal-World Example
A 25-person SaaS company uses this to catch bug reports from their #customer-feedback and #dev channels. Before automation, 30% of reported issues got buried in chat history and never made it to their product backlog. Now every message tagged with 🐛 or 💡 becomes a Trello card within 30 seconds.
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
Import this workflow directly into Make
Copy the pre-built Make blueprint and paste it straight into Make. All modules, filters, and field mappings are already configured — you just need to connect your accounts.
Before You Start
Make sure you have everything ready.
Field Mapping
Map these fields between your apps.
| Field | API Name | |
|---|---|---|
| Required | ||
| Card Name | ||
| Card Description | ||
| Board Position | ||
3 optional fields▸ show
| Labels | |
| Assigned Members | |
| Due Date |
Step-by-Step Setup
Dashboard > Create a new scenario
Create New Scenario in Make
Log into Make and click Create a new scenario from your dashboard. You'll see the visual scenario builder with a large plus icon in the center. Click it to add your first module. This starts the automation workflow.
- 1Click 'Create a new scenario' from Make dashboard
- 2Click the large + icon in the scenario builder
- 3Search for 'Slack' in the app list
- 4Select 'Watch Messages' trigger
Slack Module > Connection > Channel Selection
Configure Slack Trigger
Connect your Slack workspace by clicking Create a connection. Make will open Slack's OAuth flow in a new tab. Choose the specific channel where bug reports come in - usually #bugs, #feedback, or #product. Set the trigger to watch for new messages only.
- 1Click 'Create a connection' and authorize Make in Slack
- 2Select your target channel from the dropdown
- 3Set 'Watch for' to 'New messages only'
- 4Leave 'Include replies' unchecked unless you want thread responses
Module Connector > Filter > Condition
Add Message Filter Logic
Click the wrench icon between modules to add a filter. Set up conditions to catch bug reports and feature requests. Look for emoji triggers like 🐛 for bugs or 💡 for features, or specific keywords like 'bug', 'issue', 'feature request'. This prevents every message from creating a Trello card.
- 1Click the wrench icon between Slack and the next module
- 2Click 'Set up a filter'
- 3Set condition: Text contains '🐛' OR '💡' OR 'bug' OR 'feature'
- 4Name the filter 'Bug and Feature Filter'
📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}Add Module > Text Parser > Match Pattern
Add Text Parser for Classification
Add a Text Parser module to determine if the message is a bug or feature request. Use pattern matching to look for bug-related keywords versus feature-related ones. This will help assign the right labels and team members in Trello later.
- 1Click + to add another module after the filter
- 2Search for 'Text parser' and select it
- 3Choose 'Match pattern' as the function
- 4Set Text to {{1.text}} from Slack
- 5Set Pattern to match bug keywords: (bug|error|broken|crash)
Add Module > Trello > Create a Card
Connect Trello Integration
Add a Trello module and choose Create a Card action. Click Create a connection and authorize Make to access your Trello account. Select the board where you track bugs and features - typically your product backlog or development board. Choose the appropriate list for new items.
- 1Click + and search for 'Trello'
- 2Select 'Create a Card' action
- 3Click 'Create a connection' and authorize in Trello
- 4Select your target board from the dropdown
- 5Choose the list for new cards (usually 'Backlog' or 'To Do')
Trello Module > Card Fields
Map Card Title and Description
Configure the Trello card fields using Slack message data. Set the card name to include the message type and a preview. Use the full message text as the description. Add the Slack user who reported it and a link back to the original message for context.
- 1Set Name field to: '[BUG] {{1.text}} (first 50 chars)'
- 2Set Description to include full message: {{1.text}}
- 3Add 'Reported by: {{1.user.real_name}}' to description
- 4Include Slack permalink: {{1.permalink}}
Use this formula in the Card Name field to intelligently truncate long messages while preserving important context and adding severity indicators.
JavaScript — Custom Functionif(▸ Show code
if(
contains(lower({{1.text}}), 'critical'),
'[CRITICAL] ' + ... expand to see full code
if(
contains(lower({{1.text}}), 'critical'),
'[CRITICAL] ' +
if(
length({{1.text}}) > 60,
substring({{1.text}}, 1, 60) + '...',
{{1.text}}
),
if(
contains({{2.0}}, 'bug'),
'[BUG] ' +
if(
length({{1.text}}) > 50,
substring({{1.text}}, 1, 50) + '...',
{{1.text}}
),
'[FEATURE] ' +
if(
length({{1.text}}) > 45,
substring({{1.text}}, 1, 45) + '...',
{{1.text}}
)
)
)Trello Module > Labels > Conditional Mapping
Set Up Dynamic Labels
Configure labels based on the text parser results. If the parser found bug keywords, apply a red 'Bug' label. For feature requests, use a blue 'Feature Request' label. You'll need to create these labels in Trello first if they don't exist.
- 1Click in the Labels field
- 2Use if() function: if(contains({{2.0}}, 'bug'), 'Bug Label ID', 'Feature Label ID')
- 3Get label IDs from Trello board settings
- 4Test the conditional logic with sample data
Trello Module > Members > Assignment Rules
Add Team Assignment Logic
Set up member assignment based on keywords or channel. For bugs, assign to QA team members. For features, assign to product managers. Use conditional mapping to route different types to appropriate team members automatically.
- 1Click in Members field
- 2Add conditional assignment: if(contains({{1.text}}, 'critical'), 'Lead Dev ID', 'QA Team ID')
- 3Get member IDs from Trello team settings
- 4Set up fallback assignment for unclassified items
Trello Module > Due Date > Date Calculation
Configure Due Date Rules
Set dynamic due dates based on issue severity. Critical bugs get 1-day due dates, regular bugs get 1 week, features get 2 weeks. Use Make's date functions to calculate dates from the current timestamp when the card is created.
- 1Click in Due Date field
- 2Use addDays() function: addDays(now, if(contains({{1.text}}, 'critical'), 1, 7))
- 3Format with formatDate() for proper Trello format
- 4Test date calculations in Make's formula tester
Scenario Controls > Test > Activate
Test and Activate Scenario
Run a test with real Slack messages to verify everything works. Check that cards appear in Trello with correct labels, assignments, and due dates. Fix any field mapping errors before turning on the scenario. Once working, flip the ON switch to make it live.
- 1Click 'Run once' to test with existing data
- 2Post a test message in Slack with bug keywords
- 3Verify the Trello card was created correctly
- 4Toggle the scenario ON to activate continuous monitoring
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 Make for this if you need complex conditional logic for routing different message types to different Trello lists or team members. Make's visual router and text parsing modules handle the classification better than basic trigger platforms. The formula system lets you create dynamic due dates and card titles based on message content. Skip Make if you just want simple message-to-card creation without classification - Zapier's Slack trigger is faster to set up.
This workflow costs about 2 operations per triggered message - one for the Slack trigger, one for the Trello card creation. At 50 bug reports per month, you're looking at 100 operations total, well within Make's free tier of 1,000. Zapier charges per task too, but their Slack integration updates faster. Both platforms cost the same until you hit volume.
Zapier's Slack trigger fires 2-3 seconds faster than Make's webhook, which matters for critical bugs. n8n gives you more complex text processing options and custom regex without formula limitations. Power Automate integrates better if you're already using Microsoft Teams alongside Slack. Pipedream offers custom code for advanced message parsing that Make's built-in functions can't handle. Make wins on the visual workflow builder - seeing the routing logic makes troubleshooting easier when your filters break.
You'll hit Trello's API rate limits at around 300 cards per 10 seconds if your Slack channels get busy during incidents. Slack's webhook occasionally delivers duplicate events, so you might see duplicate cards without deduplication logic. The text parser sometimes misclassifies messages when people use ambiguous language like 'this feature is broken' - could be a bug report or feature complaint. Set up a 'Needs Review' label for edge cases your filters can't handle cleanly.
Ideas for what to build next
- →Add Status Updates Back to Slack — Create a reverse sync that posts to Slack when Trello cards move to Done, closing the feedback loop.
- →
- →Set Up Weekly Digest — Build a scheduled report that summarizes new bugs and features created each week and posts to your team channel.
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