Build deeper decision logic in one Make scenario, and keep every decision path easy to follow
Hey Makers! One of your recent favorites just got an upgrade. ![]()
Since If-else & Merge launched, it’s become the go-to for building clearer, more predictable automation paths. Now we’re taking that logic a level deeper with the new If-else & Merge functionality.
Meet Nested If-else & Merge, a new way to build multi-level conditional logic directly inside your scenarios.

New to If-else & Merge? Start here first
If-else & Merge community article
What’s new
-
Nest If-Else inside another If-Else: Add a second level of logic inside any branch, so you can model detailed rules where they belong.
-
Keep related decisions in one flow: Instead of spreading logic across chained Routers and repeated modules, you can see the full decision tree in one place.
-
Use a Merge for each nested level: Every nested If-Else closes with its own Merge module, which makes each decision level clear and easier to trace.
-
Review and update scenarios with less hunting: When rules change, you can jump to the right branch faster and understand what happens next without reading through duplicated paths.
Real-world use cases
-
Lead routing with layered rules: First split by region, then inside each region branch, route by company size or sales segment before merging back into the rest of the flow.
-
Order handling with exception paths: Check order type first, then inside a branch, apply extra conditions for stock status, shipping method, or priority customers.
-
Internal approval flows: Start with department-level decisions, then add nested logic for budget threshold, requester role, or contract type, all inside one readable scenario.
Try the Nested If-else & Merge on a scenario you already have — and let us know what clicked.
Happy automating! ![]()
Valery from Make
Helpful resources
Documentation and step-by-step guide
New to If-else & Merge? Check out the If-else & Merge community article
