How to build branching logic in Bubble workflows

You build branching logic in Bubble workflows by using Only when conditions on workflow actions (or separate event branches) so Bubble decides which action runs based on the data at that moment. Every branch is simply an action with its own Only when expression.

What Branching Logic Means in Bubble

Bubble does not have traditional “if/else blocks.” Instead, every workflow action can have an Only when condition. If that condition is true, the action runs; if not, Bubble skips it. Multiple actions can create multiple branches.

• To create “IF,” add an action with an Only when condition.
• To create “ELSE,” add another action below it with the opposite condition.
• All branches live in the same workflow, but only the matching ones run.

Step-by-Step Example

Imagine a button that should do different things depending on whether the user has a profile complete.

• Create Workflow → “When Button X is clicked”.
• Add an action: Navigate to Page “dashboard”.
  Set Only when: Current User’s profile\_complete is yes.
• Add another action: Show Popup “CompleteProfile”.
  Set Only when: Current User’s profile\_complete is no.

Now you have two clean branches. Bubble automatically runs only the matching one.

Backend Workflow Branching

Branching works the same in backend workflows. Each action can check conditions based on incoming parameters, Things, or API data.

// Example of a safe branching pattern in a backend workflow
// Action 1 runs ONLY when order total is high
Only when This Order's total > 500: send email "VIP order"

// Action 2 acts as fallback
Only when This Order's total <= 500: send email "Standard order"

Best Practices

• Keep each branch’s condition mutually exclusive to avoid both running.
• If multiple actions belong to the same branch, give all of them the same Only when condition.
• Avoid overly complex expressions; use custom states or fields if needed.

This is the most reliable way to create clear, predictable branching logic in Bubble workflows.