All Collections
Conditional Branches
Conditional Branches
Written by Hannah Hill
Updated over a week ago

Who Can Do This?

  • Dashboard Users

  • Owners

Using conditional branches in your workflow allows you to route submissions to different completers or different workflow steps based upon data that is previously collected in the workflow.

Conditional branches are an amazing tool that allow users to dynamically change the workflow route based on information from the submission. Think of conditional branches as new pathways for the submission to travel on.

To add a conditional branch to a workflow, navigate to your Workflow page.

Chart, funnel chart

Description automatically generated

Make sure your workflow is unlocked so that you are able to edit it.

Conditional branches can only work if there are steps that precede them in the workflow, so they cannot be the first step in a workflow. If you already have existing steps in your workflow, you will notice plus sign buttons in between each of your existing steps. Click on the "+" that aligns with where you want your conditional branch to be located in the workflow. You will also be able to move this step to a different part of your workflow at a later time if needed.

You will now see a selection pane on the right side of your screen where you will decide what type of step you'd like to add to your workflow. Choose Conditional Branch from this list.

Now your conditional branch appears in your workflow. Wait for the blue checkmark in the bottom right corner of your screen to confirm that your changes have been saved.

Notice that there is a red exclamation point in the left corner to remind you that it is not completely set up yet. Click on your green conditional branch to finish configuring it. Your step configurations should now appear on the right side of your screen.

First, you can change the Step Name that appears in the workflow.

Underneath your Step Name, you will see the configurations for your first branch. You can change the Branch Name to whatever you would like. Be sure to name it something that clearly differentiates this branch from any other branches and communicates what kind of submissions would be travelling down this branch.

Next, we will build the conditions that apply to this branch. If a submission meets these conditions, it will be sent down this specific branch of the workflow.

From the dropdown inside of the phrase When [any/all] of the following are true, choose Any if the submission can meet any of the following conditions to be sent down this branch of the workflow. Choose All if the submission must meet all of the following conditions to be sent down this branch of the workflow. If you are only creating one condition for this branch, what you choose in this dropdown will not matter.

Click the next dropdown to select which previous step in the workflow you are basing this conditional routing upon. When this dropdown menu is clicked, you will notice that all of the steps that exist before this conditional branch in the workflow will appear as options. For example, if you are basing this condition on data that was collected on a previous form step, you would select that form step in this dropdown.

Now that you've told your conditional branch which step of the workflow to base this condition on, we need to select a specific field of data within that step. In our example of using a form step, you will see all fields from that form listed in the next dropdown. For example, if you are basing this condition on what language preference the completer selected, you would choose the field that you labeled "Language Preference".

(*This is an example of why it is important to clearly name each of your form fields.)

Next, you can select the qualifier that you want to accompany this field of data. If you want the submission to be routed to this branch if the completer selected "English" as their language preference, we're going to choose equal to from the middle dropdown menu and type in English in the field to the right. In other words, every submission where the language preference is filled in as "English" will be routed down this conditional branch.

Notice that there are many different qualifiers you can choose from to create your conditional statement. The most frequently used options are:

  • equal to or not equal to if the field is completed by an alphabetic value

  • >, <, =>, or <= if the field is completed by a numeric value

When typing in the data that will complete the conditional statement, make sure it is typed exactly as it appears in your workflow. If a completer submits "english language" and your conditional statement is set up as equal to English, the condition will not be met and that submission will be routed down the default branch.

As a best practice, we recommend that you base your conditions upon a field that the completer cannot change the value of, such as a dropdown field, a radio group, or a checkbox field. Remember that with checkboxes and specific radio group options, the values will either be TRUE (they selected that option) or FALSE (they did not select that option).

Click the blue plus sign underneath your first condition to add an additional condition that a submission can meet in order to be routed down this branch. Click the blue minus sign to delete this condition within this branch.

To add a new conditional branch, click the purple Add Branch button at the bottom of this window. Repeat the above steps to create the conditions that you want to apply to this branch.

You can click the three dots in the top right corner of each branch to delete the entire branch.

Click the blue Save button to save your configurations.

Once you see the blue checkmark signaling that your changes have been saved, your red exclamation point will be gone, and you will be ready to add the appropriate steps to each branch.

Did this answer your question?