If you have ever built a workflow with multiple parallel branches and then struggled to test a specific path without rebuilding the whole thing - this update is for you. You can now set a default path in Advanced Builder workflows, giving you much more control over how tests run and how contacts enter from other workflows.

What's changed

In workflows with multiple parallel branches, the root node is now labelled Default Path. On the first action in any branch, you can click the branch icon to set that branch as the default. Once set, workflow tests and contacts entering from another workflow will follow that branch.

A solid trigger connector shows you which branch is currently the default path. A dashed connector means that branch is reached through a Go To connector and is not the default.

Why it matters

Before this update, testing a specific branch in a multi-branch workflow meant working around the fixed root path - which could mean rearranging steps or running incomplete tests. That added time and created room for error.

Now you can point tests exactly where you need them. Want to check how your second reminder branch behaves? Set it as the default, run the test, and get a clean result without touching the rest of your workflow.

It also makes cross-workflow entries cleaner. When a contact enters from another workflow, you have full control over which branch they land in.

How to use it

Open a workflow with multiple parallel branches in Advanced Builder. Click the branch icon on the first action of the branch you want to use as the default. Set it as the Default Path and run your test or enrollment from there.