| 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.
|
Available with: | ||||
| Marketing Automation | ✓ | ||||
| CRM Ultimate | |||||
| CRM PRO | |||||
| CRM Free | |||||
| Toolbar: | |||||
 |
|||||
| Users: | |||||
| Administrators | ✓ | ||||
| Company Managers | ✓ | ||||
| Marketing Managers | ✓ | ||||
| Sales Managers | |||||
| Salespersons | |||||
| Jr. Salespersons | |||||
Branching Workflows
Branching workflows are groups of actions originating from a single trigger. Workflows can branch in one of two ways:
|
|
|
|
|
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.
That said, the repeatability settings for a branch will override any repeatable settings of a given action within the branch. For example, if you are referencing a repeatable standalone action group within a visual workflow branch that is not repeatable, the referenced action group will be treated as not repeatable.
Branching Actions
Only certain actions can be used to create branching triggers. These options are as follows:
| Type | Action | Branching Triggers |
| Communication |
|
|
| Contact Edit |
|
|