|SharpSpring allows you to leverage branching within the Visual Workflow Builder to automatically remove leads from an action group when specific events occur, or to begin different actions based on filters applied to a single trigger.
This article will detail the concept of visual workflow branching.
Branching workflows are groups of actions originating from a single trigger. Workflows can branch in one of three ways: by filters, Yes/No filters, or by an action in a parent group.
Repeatable Branch Content
Branches differ from action groups. Reusable action groups are a collection of standalone events that can be referenced within a visual workflow or be manually scheduled to a list. Branches are not action groups.
Branches refer to a collection of actions created for use only within a visual workflow. As the name implies, this collection of actions branch out from the action group and are dependent upon additional criteria in order to function. Branches will not be added as reusable, standalone action groups.
You can make branches repeatable, however. When creating branch content in a visual workflow, clicking Make Repeatable will set a branch as repeatable.
For example, if you add a non-repeatable action group to a repeatable branch, the action group will be repeatable for people who enter the automation via that branch. However, if you add a repeatable action group to a branch that is not set as repeatable, then the action group will not be repeatable.
Only certain actions can be used to create branching triggers. These options are as follows:
Branching Actions and Yes/No Filters
Yes/No filters are unique branches that can only be added to certain places in the workflow. These places are available after:
- Time Delays