Make Adds Nested If-Else and Merge for Multi-Layer Automation Logic.

Make has released nested if-else and merge functionality, allowing automation builders to stack conditional logic several layers deep while keeping everything in a single, traceable flow. The update addresses a common pain point: scenarios that require multiple decision points but need to remain readable for teams reviewing or modifying them months later.

The feature lets users place an if-else router inside another if-else branch when a decision requires a second (or third) layer of evaluation. Each decision level can have its own dedicated merge module, so every conditional path reconnects at the appropriate point rather than forcing all branches to converge at a single endpoint.

Automation scenarios often mirror real-world business logic, which rarely fits into simple binary choices. Lead routing might check company size first, then industry, then engagement score. Order processing might evaluate product type, then inventory status, then customer tier. Before this update, builders had two options: create multiple separate scenarios with webhooks passing data between them, or build sprawling flows where similar logic repeated across disconnected branches.

Nested if-else structures keep related rules in one place. A marketing team can see an entire lead qualification process in a single canvas view. An operations manager can trace how different order types move through validation, fulfillment checks, and notification routing without hunting through multiple scenarios or following webhook chains.

The dedicated merge modules also solve a technical problem. When all conditional branches converge at a single merge point, Make has to wait for every path to complete before continuing execution. With nested merges, each decision layer can resolve independently. If a first-level condition routes to a branch that doesn't need further evaluation, that path can complete and trigger downstream actions immediately rather than waiting for unrelated branches to finish processing.

The feature arrives as Make continues expanding its capabilities for teams building complex automation infrastructure. The company recently launched transparent AI agents and introduced scenario recovery to prevent work loss from browser crashes. Nested logic fits the same pattern: reducing friction when scenarios need to scale or when multiple team members need to understand and modify automation flows.

For organizations using Zapier or n8n, nested conditionals represent a structural difference in how visual automation platforms handle complexity. Zapier's path system allows filtering but doesn't support true nesting within a single zap. n8n offers conditional routing through its If node, but merge behavior requires manual configuration. Make's approach combines the routing with purpose-built merge modules designed specifically for multi-layer decision trees.

The feature is available now to all Make users at no additional cost. Existing scenarios can be modified to incorporate nested logic without breaking current functionality, and new scenarios can use the feature immediately through the standard if-else router module.