Make's Nested If/Else: Cleaner Logic for Multi-Path Scenarios
In this hands-on tutorial, Vicente walks you through a real-world refactor of a complex lead management workflow — replacing a messy router setup with Make's new Nested If/Else module for cleaner, more reliable logic. Using his own live scenario as the canvas, he shows you exactly how to think through branching conditions and reduce redundancy in multi-path flows.
🔍 Inside the Build:
* Why If/Else Over Router: Vicente breaks down the key difference — If/Else guarantees a single path is taken, eliminating the risk of overlapping conditions that routers can fall into.
* The Real Scenario: A lead management system that receives Slack responses, processes actions in HubSpot and Airtable, and needs to branch based on whether a lead is approved, needs more info, or is rejected.
* Nesting in Practice: See how Vicente layers a second If/Else inside the Else branch to handle the "more info vs. rejection" split — keeping conditions clean and exclusive.
* Using Merge to Consolidate Paths: Learn how to bring diverging branches back together with a Merge module, avoiding duplicated email-sending logic across paths.
* Live Test & Mapping: Vicente runs the refactored scenario in real time, fixes unmapped variables on the fly, and confirms all three paths execute correctly.
Vicente's goal is to turn a sprawling, hard-to-maintain router flow into a lean, readable structure. This is essential watching for anyone building multi-path automations who wants cleaner scenarios and fewer maintenance headaches.
🛠️ Featured Stack:
* Make Nested If/Else Module (Conditional Logic)
* Make Merge Module (Path Consolidation)
* HubSpot (Deal & Contact Creation)
* Airtable (Record Updates)
* Slack (Webhook Trigger / Lead Input)
💡 Pro-Tip from Vicente: "I think If/Else is the way to go in 99% of the cases." By nesting conditions instead of stacking router paths, you eliminate the risk of a bundle accidentally triggering multiple branches — and your scenario becomes far easier to read, debug, and hand off to a teammate. 🔗 Make
https://www.youtube.com/watch?v=Lg42RNGYhaY&utm_source=dlvr.it&utm_medium=blogger
🔍 Inside the Build:
* Why If/Else Over Router: Vicente breaks down the key difference — If/Else guarantees a single path is taken, eliminating the risk of overlapping conditions that routers can fall into.
* The Real Scenario: A lead management system that receives Slack responses, processes actions in HubSpot and Airtable, and needs to branch based on whether a lead is approved, needs more info, or is rejected.
* Nesting in Practice: See how Vicente layers a second If/Else inside the Else branch to handle the "more info vs. rejection" split — keeping conditions clean and exclusive.
* Using Merge to Consolidate Paths: Learn how to bring diverging branches back together with a Merge module, avoiding duplicated email-sending logic across paths.
* Live Test & Mapping: Vicente runs the refactored scenario in real time, fixes unmapped variables on the fly, and confirms all three paths execute correctly.
Vicente's goal is to turn a sprawling, hard-to-maintain router flow into a lean, readable structure. This is essential watching for anyone building multi-path automations who wants cleaner scenarios and fewer maintenance headaches.
🛠️ Featured Stack:
* Make Nested If/Else Module (Conditional Logic)
* Make Merge Module (Path Consolidation)
* HubSpot (Deal & Contact Creation)
* Airtable (Record Updates)
* Slack (Webhook Trigger / Lead Input)
💡 Pro-Tip from Vicente: "I think If/Else is the way to go in 99% of the cases." By nesting conditions instead of stacking router paths, you eliminate the risk of a bundle accidentally triggering multiple branches — and your scenario becomes far easier to read, debug, and hand off to a teammate. 🔗 Make
https://www.youtube.com/watch?v=Lg42RNGYhaY&utm_source=dlvr.it&utm_medium=blogger

