🔍 Summary

Introduce the ability to build nested conditional logic (if/else blocks inside other if/else branches), enabling more advanced and organized automation logic without duplicating workflows or creating long, flat sequences.

🧩 Problem

The current If/Else structure is single-layered, forcing users to:

Chain flat logic with lots of redundant conditions

Create additional workflows or custom workarounds to simulate nesting

Duplicate logic just to change small branch outcomes

This creates inefficiency, increases the chance of configuration error, and limits logical flexibility—especially in use cases like sales funnels, custom follow-up routines, or multi-segment journeys.

💡 Proposed Solution

Allow users to drag and drop new If/Else nodes inside existing If/Else branches, supporting:

Visual indentation or collapse/expand nesting view

Unlimited (or reasonably capped) levels of nested logic

Copy/paste logic blocks between nested nodes

Seamless evaluation: child branches only process if the parent is true

UI Suggestions:

Use collapsible tree-style branches (like nested folders)

Visual guides (e.g., connector lines or “inside branch of…” indicators)

Ability to nest under “Yes” or “No” conditions

✅ Use Cases

Multi-Tier Follow-Up Systems

If Contact Type = Lead

→ If Follow-Up Type = 2 Weeks

→ If Follow-Up Date is today

→ Send reminders

→ Assign task

→ Else: Skip

→ Else: Tag for manual review

Else If Contact Type = Client

→ Archive old tags

→ Remove from nurture workflows

Advanced Qualification Flows

If Form A is submitted

→ If score > 80

→ If location = California

→ Send to high-priority sales queue

→ Else: Assign regional SDR

→ Else: Send to nurture

Redundant Workflow Elimination

Instead of creating separate workflows for minor logic changes, use nested paths for improved maintainability.

🛠 Technical Considerations (Optional for Devs)

Execution engine must support condition trees

Logging/Execution history should display nested paths clearly

Backward compatibility: no change required for existing flat workflows

🚦Priority Justification

Reduces workflow bloat

Minimizes logic duplication

Makes workflows easier to build, test, and maintain

Empowers advanced users to consolidate decision trees into single flows

Brings GHL in line with major automation platforms like Integromat, Zapier, and ActiveCampaign