Automation Branching: Build Smart Customer Journeys in One Flow
Stop managing 8 separate automations. Kajabi's branching lets you build one flow with multiple smart paths based on customer behavior.

Summary
Kajabi's automation branching lets you build one automation that handles every customer path. Instead of maintaining ten or more separate flows, you build one that branches based on what each customer actually does. This article walks through five real patterns, how to build your first one, and the mistakes to avoid.
If you've been running your Kajabi business for any length of time, you probably have a secret shame: the automations tab.
Ten separate automations. Maybe fifteen. Some of them do basically the same thing with slight variations. A few you're afraid to touch because you can't remember what they do. One that might be broken but you're not sure.
Sound familiar?
Here's the problem: before branching, every customer path needed its own automation. A buyer who chose the monthly plan got one sequence. Annual plan buyers got another. Free trial users got a third. And if you wanted to further segment by engagement level? That's three more automations.
It multiplied fast. And the more automations you had, the harder it was to see the full picture of your customer journey.
Automation branching changes this. One automation, multiple paths. The flow branches based on what your customer actually does (which plan they chose, what they bought, how they engaged) and routes them down the right path automatically.
What Branching Actually Looks Like
Think of it like a choose-your-own-adventure book for your customer journey.
A customer hits a trigger (purchases a product, signs up for a trial, joins your community). Instead of that trigger firing one linear sequence, it enters a branching flow:
Branch point: "Which pricing option did they select?"
- Monthly: Welcome email + check-in at Day 7 + upgrade offer at Day 21
- Annual: Welcome email + bonus content unlock + loyalty gift at Day 30
- Payment plan: Welcome email + payment reminder sequence + completion celebration
All of this lives in one automation. One place to see it. One place to edit it. One place to troubleshoot.
Five Branching Patterns That Replace 10+ Automations
Pattern 1: The Pricing-Based Welcome Sequence
Trigger: Product purchase.
Branch on: Pricing option selected.
Instead of building separate welcome sequences for each pricing tier, build one that branches based on commitment level. Monthly subscribers get more touch-points (they need more convincing to stay). Annual subscribers get bonus content (reward their commitment). Payment plan users get specific messaging around their payment schedule.
Replaces: 3-4 separate welcome automations
Pattern 2: The Engagement-Based Nurture Path
Trigger: Email open / link click / course progress.
Branch on: Engagement level.
Active members who open every email and complete lessons on time get one path (advanced content, upsell opportunities, community invitations). Inactive members who haven't logged in for 7 days get a different path (re-engagement emails, "need help?" check-ins, simplified next steps).
Replaces: 2-3 engagement automations + manual segment management
Pattern 3: The Post-Purchase Upsell Router
Trigger: Product purchase.
Branch on: What they already own.
A customer buys your introductory course. The automation checks: do they already own your advanced course? If yes, route them to the community upsell. If no, route them to the advanced course offer. Own both? Route them to your coaching upsell.
Replaces: Multiple upsell automations with manual exclusion lists
Pattern 4: The Win-Back Decision Tree
Trigger: Subscription cancellation.
Branch on: How long they were a member + cancellation reason.
A member who cancels after 30 days gets a different win-back approach than someone who was with you for a year. Combined with Kajabi's new cancellation reason tracking, you can branch on WHY they left: too expensive (offer discount), not enough time (offer pause), found something else (competitive comparison), finished the content (new product offer).
Replaces: 3-5 separate win-back automations
Pattern 5: The Event-Triggered Segmentation Flow
Trigger: Form submission / tag addition.
Branch on: Form responses or tag combinations.
Someone fills out your onboarding survey. Based on their answers (beginner vs. advanced, course vs. coaching interest, budget range), they're routed into the right nurture path. No manual segmentation. No separate automations per segment.
Replaces: As many automations as you have segments (often 4-6)
How to Build Your First Branching Automation
Step 1: Map the journey on paper first. Draw the trigger, the decision points, and the paths. Keep it to 2-3 branches to start.
Step 2: Open the automation builder. Create a new automation with your trigger.
Step 3: Add a branching node. Select the condition for branching (pricing option, tag, engagement, custom field, etc.).
Step 4: Build each path. Add the emails, waits, actions, and tags for each branch independently.
Step 5: Test each path. Use a test contact to verify each branch fires correctly.
Step 6: Archive the old automations. Once your branching automation is live and tested, turn off the separate automations it replaces. Don't delete them right away, archive for 30 days in case you need to reference them.
Common Mistakes to Avoid
Don't over-branch. Start with 2-3 paths. You can always add more later. A branching automation with 8 paths is just as confusing as 8 separate automations.
Don't forget the default path. Every branch point should have a "none of the above" path for contacts who don't match any condition. Otherwise they fall out of the automation entirely.
Don't skip the wait nodes. Branching makes it tempting to fire everything immediately. Use Kajabi's improved wait nodes (schedule by date, day, or time) to pace your communication.
The Payoff
Here's what changes when you consolidate to branching automations:
- Visibility: See your entire customer journey in one view
- Maintenance: Update one automation instead of ten
- Consistency: Ensure no customer falls through the cracks between automations
- Sophistication: Create journeys that respond to real behavior, not just time delays
One automation. Multiple paths. Zero duplicate workflows.