Set up workflow branching to route records down different paths

Workflow Branching lets you create different paths within a single workflow based on a record’s information. Instead of creating separate workflows for each type of record, you can create one workflow and use branches to decide which follow-up actions each record should receive.

For example, you could use a branch to send absentee owners an SMS sequence while sending owner-occupied properties an email sequence—all from the same workflow.

You can add a branch anywhere in a workflow, including as the very first step. Each branch can have up to 20 paths, and you can nest branches up to three levels deep.

How workflow branching works

Think of a branch as a decision point in your workflow.

When a record reaches a branch, Invelo checks the paths from top to bottom. The record enters the first path whose filter it matches.

If the record doesn't match any of the configured paths, it automatically goes into the default path.

Once the record enters a path, it stays on that path for the rest of that workflow run. When the path is finished, the record continues with the next steps in the main workflow.

For example:

Workflow starts → Branch → Path actions → Continue main workflow

Invelo checks a record's information when it reaches the branch. After the record enters a path, it will not switch to another path if the record's information changes later.

If the record is enrolled in the workflow again, its information is checked again and it may take a different path.

Set up a branch

1. Add a branch to your workflow

You can add a branch anywhere in your workflow, including:

• Before the first action
• Between existing actions
• Inside another branch path

When you add a branch, Invelo automatically creates:

• One configured path for you to set up
• One default path

A branch added as the first step routes records as soon as they enroll in the workflow.

2. Create and configure your paths

For each configured path, you can:

• Give the path a name
• Add a filter to determine which records enter the path
• Add actions that should run for those records

You can create up to 20 paths per branch.

You must always have at least one configured path and the default path.

3. Use the default path

Every branch has a default path.

The default path does not have a filter. Instead, it catches any record that doesn't match the filters of your other paths.

The default path:

• Cannot be deleted
• Always stays at the bottom of the path list
• Can be renamed
• Can contain its own actions
• Can be left empty

You can save and activate a path even if it doesn't contain any actions. Records that enter an empty path simply continue to the next step after the branch.

4. Arrange your paths in the right order

You can drag and drop your paths to change their order.

The order is important. If a record matches more than one path, it will always enter the path that appears first.

For example, if your paths are:

1. High Equity
2. Absentee Owner
3. Vacant Property
4. Default

And a record matches both High Equity and Absentee Owner, it will enter the High Equity path because it appears first.

The default path will always remain last.

5. Add actions to each path

Each path can have its own actions.

For example:

High Equity path

• Send an SMS
• Wait 2 days
• Create a task

Absentee Owner path

• Send an email
• Wait 5 days
• Create a task

After the record finishes the actions in its path, it continues to the steps that come after the branch in your main workflow.

Add branches within other branches

You can add another branch inside an existing path if you need more specific routing.

For example:

Branch 1: Owner Type

• Absentee Owner
  • Branch 2: Equity
    • High Equity
    • Low Equity
• Owner Occupied
• Default

You can nest branches up to three levels deep. Once a branch is three levels deep, you cannot add another branch inside it.

How records choose a path

When a record reaches a branch, it follows these rules:

• If it matches one path: The record enters that path and runs its actions. Once the path ends, the record continues with the rest of the workflow.

• If it matches multiple paths: The record enters the first matching path based on the order of your paths.
  
  This is why it's important to place your paths in the correct order.

• If it doesn't match any path: The record enters the default path.

• If the path has no actions: The record simply passes through the path and continues with the rest of the workflow.

• If the record changes after entering a path: The record stays on its original path.

  For example, imagine a record enters your "Low Equity" path. Later, the record's equity changes and it now meets the filter for your "High Equity" path.

  The record will not move to High Equity. It stays in Low Equity for the remainder of that workflow run.

  If you re-enroll the record, Invelo checks the filters again, so it could enter a different path.

• If you pause and resume the workflow: Pausing and resuming a workflow does not change a record's path.

• If you unenroll a record: If you unenroll a record while it is partway through a path, its remaining actions are canceled, just as they are with other workflow actions.

Tips for setting up workflow branching

Keep these tips in mind when building your branches:

• Put your most specific paths first. Because records follow the first matching path, place more specific filters above broader ones.

• Use clear path names. Names like "High Equity" or "Absentee Owner" make it easier to understand what each path is for.

   

• Don't forget the default path. Think about what should happen to records that don't match any of your configured paths.

• Remember that path selection is permanent for that workflow run. A record won't switch paths if its information changes after it has already been routed.

• Use path counts to monitor your workflow. The number of records in each path can help you understand how your workflow is distributing records.

   

Conclusion

Workflow Branching gives you more flexibility without requiring you to build multiple workflows for similar follow-up sequences. You can create different paths, use filters to determine which records enter each path, and customize the actions each group receives.

Need Help?

Need help setting up your workflow or deciding how to structure your branches? Contact our Support team via the in-app chat or send an email at support@inveloapp.com and we'll be happy to help you get your workflow set up correctly.