What’s new?

You can now change the Default Path in Advanced Builder workflows. In workflows with multiple parallel branches, this lets you choose which branch contacts enter by default when they come from another workflow or when you run a workflow test.

How it works

The root node is now labeled Default Path. On the first action in each branch, you can click the branch icon to set that branch as the default path. Once selected, workflow tests and contacts entering from other workflows will follow that branch.

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.

• Set that branch as the Default Path and run your test or enrollment.

Why we built it

Testing and configuring workflows with parallel branches was harder when only one root path handled workflow tests and cross-workflow entries. This update gives you more control, makes branch-level testing easier, and helps you validate each path without rearranging your workflow.

Simple example

When testing a workflow with multiple reminder branches, you can set one branch as the Default Path so your test contact enters that specific branch first.

Additional Notes

• The root node is now called Default Path in Advanced Builder workflows with multiple parallel branches.

• You can set the default path from the first action in any branch using the branch icon, with tooltips to explain the behavior.

• The default path is used for workflow tests and for contacts entering from another workflow.

• A solid trigger connector means the branch is the Default Path. A dashed trigger connector means the branch is reached through a Go To connector and is not the default path.

Preview