How to Automate Lead Prioritization with Make.com's New If-Else and Merge Modules
Most businesses waste hours manually sorting through leads - deciding which ones warrant executive attention. With Make.com's new If-Else and Merge modules, you can automatically route high-value leads to your CEO while filtering others - all in one streamlined workflow.
The Lead Prioritization Problem
Every sales team faces the same challenge: how to efficiently separate high-value leads that deserve executive attention from the rest. Manually reviewing each lead's details and deciding who to notify is time-consuming and inconsistent.
The demo workflow solves this by automatically routing leads based on their self-reported monthly revenue. At the 2:15 mark in the video, you'll see how this eliminates guesswork - leads reporting $250K+ monthly revenue automatically trigger CEO notifications, while others follow a standard sales process.
Key insight: Businesses using automated lead prioritization see 37% faster response times to high-value leads compared to manual sorting methods.
How the If-Else Module Works
The If-Else module introduces conditional branching to Make.com workflows. Unlike traditional routers that create multiple parallel paths, If-Else creates just two branches:
- The "If" path - executed when your specified conditions are met
- The "Else" path - followed for all other cases
In our lead prioritization example, the condition checks whether the lead's monthly revenue matches certain high-value thresholds ($100K-$250K or $250K+). If true, the workflow notifies both sales and the CEO. If false, it only notifies sales.
Setting Up Your Filter Conditions
Configuring the If-Else filter is similar to setting up filters in other Make.com modules. At 3:40 in the video, you'll see the exact filter setup for our lead prioritization workflow:
Filter logic: If [Monthly Revenue] equals "$100K-$250K per month" OR equals "$250K per month plus" → route to high-value path
You can create more complex conditions using AND/OR logic, numeric comparisons, or text matching. The key is ensuring your conditions clearly distinguish between the two paths you want to create.
The Power of the Merge Module
What makes the If-Else module truly powerful is its pairing with the new Merge module. While routers create permanent branches, If-Else routes can be reconnected later in the workflow.
At 5:15 in the demo, you'll see how the Merge module lets both paths reunite to log the lead details, while maintaining a record of which path was taken (via the "CEO notified" true/false flag).
Implementation tip: Name your Merge output clearly (like "CEO_notified") so you can easily reference it in later steps.
Router vs. If-Else: Key Differences
At 6:30, the video highlights critical differences between routers and the new If-Else module:
| Feature | Router | If-Else |
|---|---|---|
| Number of branches | Unlimited | Exactly 2 (If + Else) |
| Can branches merge later? | No | Yes (with Merge module) |
| Best for | Parallel processing | Binary decisions |
Choose routers when you need multiple independent paths. Use If-Else when you want to temporarily split processing based on a condition, then reunite the workflow.
Real-World Implementation Example
The demo shows a complete implementation using a Google Form for lead intake. Key components:
- Form submission trigger - captures lead details
- If-Else module - routes based on revenue
- Notification steps - different paths notify different teams
- Merge module - reunites paths for final logging
- Google Sheets log - records all details plus which path was taken
At 8:45, you'll see how the spreadsheet formulas categorize leads by priority based on revenue, with the video troubleshooting a formula error that serves as a good learning example.
Common Pitfalls to Avoid
When implementing If-Else and Merge modules:
- Don't try to merge router branches - Merge only works with If-Else routes
- Ensure clear conditions - Ambiguous filters lead to unexpected routing
- Test both paths - Verify your If and Else branches work as intended
- Watch data modifications - Changes in one path don't automatically reflect in the other
The spreadsheet formula error at 10:20 demonstrates why testing both paths is crucial - the "very high" priority path wasn't properly handled until the formula was corrected.
Watch the Full Tutorial
See the complete workflow in action, including the troubleshooting moment at 10:20 where we fix the priority categorization formula in the Google Sheet. The video walks through every step from form submission to final logging.
Key Takeaways
Make.com's new If-Else and Merge modules provide powerful new ways to create conditional workflows that can reunite after processing differences.
In summary: Use If-Else for binary decisions where you want to temporarily split processing, then Merge to reunite the workflow. This is perfect for lead prioritization, tiered support routing, and other conditional workflows where you need different processing for different cases but want to maintain a single workflow structure.
Frequently Asked Questions
Common questions about Make.com's If-Else and Merge modules
The key difference is that routes created with the If-Else module can be merged back together later in the workflow using the Merge module, while router branches cannot be merged.
Routers allow for multiple parallel branches, but If-Else is designed for simple binary decisions with potential reconnection points. If you need to process items differently based on a condition but then bring them back together, If-Else with Merge is the better choice.
- Router: Multiple independent paths, no merging
- If-Else: Two paths (If + Else) that can merge later
- Choose based on whether you need paths to reunite
No, the Merge module only works with routes created by the If-Else module. This is a fundamental limitation of how these modules are designed.
The If-Else module maintains connection points that the Merge module can recognize and reconnect, while router branches operate independently without this capability. Attempting to merge router branches will result in an error.
- Merge only works with If-Else routes
- Router branches cannot be merged
- Plan your workflow accordingly
These modules are incredibly versatile for any workflow where you need to temporarily split processing based on conditions but want to reunite the workflow paths later.
Common applications include lead prioritization (as shown in our example), tiered customer support routing, conditional approval workflows, and processing different customer segments differently while maintaining a unified logging system.
- Lead routing: Different paths for high-value vs regular leads
- Support tickets: VIP vs standard customer handling
- Approvals: Auto-approve under threshold, manual over
- Segmentation: Different processing for different groups
Setting up the filter condition follows the same pattern as other Make.com filters. You'll define your condition using the visual filter builder interface.
For our lead prioritization example, we checked if the monthly revenue field matched certain high-value thresholds. You can create more complex conditions using AND/OR logic, numeric comparisons, text matching, and other standard filter operations.
- Use the visual filter builder interface
- Test your conditions thoroughly
- Consider edge cases in your logic
The If-Else module currently only supports two paths - the 'if' path when conditions are met, and the 'else' path for all other cases. This is by design for simplicity and reliable merging.
For more complex branching needs, you would still need to use a router module. However, you can nest If-Else modules to create more complex decision trees if needed, though this can make workflows harder to maintain.
- If-Else: Exactly two paths (if + else)
- Router: Multiple parallel paths
- Choose based on your branching needs
The Merge module doesn't automatically combine or reconcile data modifications from both paths - it simply allows the workflow to continue from the merging point.
Any data modifications would need to be handled carefully in your workflow design. Best practice is to have each path modify different data fields, or implement logic to handle potential conflicts if both paths modify the same field differently.
- Merge doesn't reconcile data changes
- Design workflows to avoid field conflicts
- Test scenarios where both paths modify data
The main limitations are that If-Else only supports binary branching (unlike routers which support multiple paths), and Merge can only be used with If-Else routes.
Also, these features were in beta as of March 2026, so functionality may evolve. Performance with very complex nested If-Else structures may need testing, and there may be limits on how far apart in the workflow the merge can occur.
- Binary branching only
- Merge only works with If-Else
- Beta status means features may change
GrowwStacks specializes in building custom Make.com workflows tailored to your business processes. Our automation experts can design intelligent lead routing systems that save your team hours of manual sorting.
We'll configure If-Else and Merge modules for your specific needs, ensuring seamless integration with your existing CRM and tools. Whether you need simple lead prioritization or complex conditional workflows, we can implement a solution that fits your exact requirements.
- Custom workflow design for your business needs
- Seamless integration with your existing tools
- Free consultation to discuss your automation goals
- Ongoing support to ensure success
Ready to Automate Your Lead Prioritization?
Don't let high-value leads slip through the cracks while your team wastes time on manual sorting. GrowwStacks can build you a custom Make.com workflow that automatically routes leads based on your specific criteria - with CEO notifications for your most valuable prospects.