branch

branch nodes implement conditional routing inside an app graph.

Summary

• Placement: Mid-flow.
• Context: Client apps and backend apps.
• Visual: No.
• Level: Easy.
• Purpose: Split traffic into personalized paths based on state and behavior.

• Evaluate expressions against $state, scores, or event payloads to select a path.
• Offer fallbacks for unmatched conditions to avoid broken flows.
• Support operators such as comparison, in, boolean logic, and null checks for expressive routing.
• You can add as many named exits as you need (for example win, lose, retry) to reflect the paths in your marketing narrative without stacking extra logic nodes.
• When configuring a branch, simply list each outcome, describe its condition, and pick the next node. A final “else” row catches all remaining users so nobody falls out of the flow.