Branch by Value
The Branch by value actionA tool for building the processes, logic, and direction within workflows. directs your workflow to perform different actions, depending on the value of a text variable.
At the Branch by value action, the workflow splits into two or more paths, or branches. When the workflow runs, it chooses which branch to use according to the value of the variable you configure:
- If the value exactly matches the name of a branch, the workflow chooses that branch.
- If the value matches no branch names, it chooses the default branch.
For example, using the “Inquiry type” field of a customer contact form to decide whether to contact Sales or Support.”
You can also add as many branches as you need.
If you want to choose the branch based on a more complex condition, see Branch by condition.
![]() |
To master the use of the Logic and flow actions, take the SELF: Workflow Complex Logic - Nintex Workflow Cloud course in Nintex University. |

Variables are placeholders that store information that changes each time the workflow runs or even during execution of a single workflow instance. To view a list of all variables that you can use in the workflow, access the Variables pane.Variables pane

The data types of variables are as follows:
- Text: Text string (with optional default value)
- Decimal: Integer numerical with a decimal point (with optional default value)
- Integer: Integer numerical with no decimal (with optional default value)
- Boolean: Yes or No (with optional default value)
- DateTime: YYYY-MM-DD, HH:MM AM/PM (with optional default value)
- Collection: A variable that groups one or more related variables of the same type into an ordered list.
- File: Path to a file. Use this variable type to attach files to email messages. A file path must start with the root folder and end with the file name. Example: /Draft/Contracts/ACME.docx
- Object: A variable that groups several related variables of any type into a hierarchical structure. Objects can contain other Objects.
- Collection of objects: A variable that groups a list of Objects of the same variable structure into a list.
For example, a collection variable named Company name can hold a list of names, such as Safalo, Nintex, and Drawloop.
For example, an Object variable named Company can hold a list of parameters, such as Company name, Email, Address, and Phone number.
Note: Objects can't be created or modified in the Variables panel.
For example, a Collection of object variable named Company details can hold a series of objects, detailing Company name, Email, Address, and Phone number for each Company name Safalo, Nintex, and Drawloop.
Note: You can assign only the variable type that a workflow expects. For example, if you want to capture a Date entry in a form, then you must create a variable of the DateTime type.

In Nintex Workflow Cloud, variables are classified as follows:
- Workflow variable
Workflow variables include those that you create and define when you configure an action. These variables store values such as collections, path to files, workflow outputsVariable to store a value or file on completion of the workflow. Set up as a user-defined variable., and other data for use throughout the workflow.
-
Start event variable
These variables capture data that are present when the workflow starts.
Range of Start event variables
Depending on the Start events you select, one or more of the following start event variables may be available.
- Form field variables capture data that user enters in the fields of a form. These variables are generated when you create a form control. An example is a variable that holds an email address entered into a web form (Nintex - Form).
-
Start event context variables, such as an identifier for the selected object (app start events). These variables are passed to the workflow as Start event context variables. Example: an object variable called Workflow Initiator that corresponds to the user who triggered to start a workflow. (Available only in Nintex - Form start event)
- Variables with applied formulas are variables that hold calculated values based on the formula defined in the Formula builder. An example is a variable that holds the calculated number of days between two DateTime variables.
- Provided start event variables such as the names of new files that trigger the workflow to run (new file start events; these variables must be explicitly added for use later in the workflow). (Available only in start events using third-party connectors such as Salesforce and Box.)
- Custom start event variables that you create, such as files or data that you want to pass as inputsVariable to store a value or file when the workflow starts. Set up as a start event variable. to a Component workflowA workflow that can be started from outside the tenancy; the workflow uses the "Component workflow" start event.. (Available only in Nintex - Component Workflow start event)
-
Context variable
These variables represent data that are related to the current workflow instanceAn occurrence of a workflow. such as Current date (DateTime), Current date and time (DateTime), Workflow instance ID (Text), Workflow name (Text), and Workflow ID (Text).
- Form-based task variable
-
Form variables - Variables that correspond to controls that you add to a form. Form variables are used only when assignees respond to a task, wherein they select an outcome and fill in a form. Form variables for the Assign a task to multiple users action are found in the Task responses collection.
-
Form URL - A variable that contains the form URL that an assignee can use to access a form.
-
Task name (Form link) - A variable that contains a hyperlink to the form URL using the Task name.
These variables capture data that are entered in forms as part of a Form-based task. The following form-based task variables are generated automatically when you configure the Form field for the action:
-
You can use Form URL and Task name (Form link) variables only within the same action.
-
To find the Task responses collection in the Insert variables panel or Variables panel, click the task name for the Assign a task to multiple users action > task name (Object) > Task responses collection. The Task responses collection also includes the Task responder and Outcome variables.
-
To access individual responses or form control values, use the Loop for each action.

You can add actions to create branches such as Branch by stage or to contain other actions such as Action Set that can be collapsed down into a single action high-level view.

You can insert existing variables into configuration fields for workflow actions and you can create user-defined variables for use throughout your workflow. Depending on the selected start event, you may be able to add provided start event variables or create your own.

Each field that accepts variables accommodates one or more methods for inserting variables. Some fields allow you to type ahead and select from a filtered list of existing variables while others require selection from a drop-down list or from the Insert variables dialog box.
In the Action configuration panel, do one of the following.
- Select an existing variable from a filtered list:
- In fields that accept variables, type [[.
Continue typing to filter the list of displayed variables.
Click the variable you want.
A drop-down list of existing variables appears.
Note: If you want to type two opening square bracket characters instead of displaying existing variables from a filtered list, press Esc and the variables list disappears.
-
Select an existing variable from the drop-down list for the field.
-
Select a new or existing variable from the Insert variables dialog box:
-
Either click + Insert or click Add variable from the drop-down list.
The Insert variables dialog box appears.
-
To create and insert a variable
- Click the Workflow tab.
- Click
Create variable.
- For Name, type the internal name you want to use.
-
For Type, select a variable type corresponding to the type of data you want to store.
Variable types
- Text: Text string (with optional default value)
- Decimal: Integer numerical with a decimal point (with optional default value)
- Integer: Integer numerical with no decimal (with optional default value)
- Boolean: Yes or No (with optional default value)
- DateTime: YYYY-MM-DD, HH:MM AM/PM (with optional default value)
- Collection: A variable that groups one or more related variables of the same type into an ordered list.
- File: Path to a file. Use this variable type to attach files to email messages. A file path must start with the root folder and end with the file name. Example: /Draft/Contracts/ACME.docx
- Object: A variable that groups several related variables of any type into a hierarchical structure. Objects can contain other Objects.
- Collection of objects: A variable that groups a list of Objects of the same variable structure into a list.
For example, a collection variable named Company name can hold a list of names, such as Safalo, Nintex, and Drawloop.
For example, an Object variable named Company can hold a list of parameters, such as Company name, Email, Address, and Phone number.
Note: Objects can't be created or modified in the Variables panel.
For example, a Collection of object variable named Company details can hold a series of objects, detailing Company name, Email, Address, and Phone number for each Company name Safalo, Nintex, and Drawloop.
-
For Default value, if relevant, update the provided default value.
-
For Component workflowsA workflow that can be started from outside the tenancy; the workflow uses the "Component workflow" start event.: To mark the variable as a workflow outputVariable to store a value or file on completion of the workflow. Set up as a user-defined variable., select the Output check box.
For more information about these fields, see Toolbar.
- Click Create & insert.
The Insert variables panel appears.
Note: The Create variable button is available only if you have previously created a variable.
The Create variable dialog box appears.
The new variable appears in the configuration field.
-

You can create user-defined variables from the action configuration panel when you're configuring a workflow action or from the toolbar of the workflow designer.

Each field that accepts variables accommodates one or more methods for inserting variables. Some fields allow you to type ahead and select from a filtered list of existing variables while others require selection from a drop-down list or from the Insert variables dialog box.
In the Action configuration panel, do one of the following.
- Select an existing variable from a filtered list:
- In fields that accept variables, type [[.
Continue typing to filter the list of displayed variables.
Click the variable you want.
A drop-down list of existing variables appears.
Note: If you want to type two opening square bracket characters instead of displaying existing variables from a filtered list, press Esc and the variables list disappears.
-
Select an existing variable from the drop-down list for the field.
-
Select a new or existing variable from the Insert variables dialog box:
-
Either click + Insert or click Add variable from the drop-down list.
The Insert variables dialog box appears.
-
To create and insert a variable
- Click the Workflow tab.
- Click
Create variable.
- For Name, type the internal name you want to use.
-
For Type, select a variable type corresponding to the type of data you want to store.
Variable types
- Text: Text string (with optional default value)
- Decimal: Integer numerical with a decimal point (with optional default value)
- Integer: Integer numerical with no decimal (with optional default value)
- Boolean: Yes or No (with optional default value)
- DateTime: YYYY-MM-DD, HH:MM AM/PM (with optional default value)
- Collection: A variable that groups one or more related variables of the same type into an ordered list.
- File: Path to a file. Use this variable type to attach files to email messages. A file path must start with the root folder and end with the file name. Example: /Draft/Contracts/ACME.docx
- Object: A variable that groups several related variables of any type into a hierarchical structure. Objects can contain other Objects.
- Collection of objects: A variable that groups a list of Objects of the same variable structure into a list.
For example, a collection variable named Company name can hold a list of names, such as Safalo, Nintex, and Drawloop.
For example, an Object variable named Company can hold a list of parameters, such as Company name, Email, Address, and Phone number.
Note: Objects can't be created or modified in the Variables panel.
For example, a Collection of object variable named Company details can hold a series of objects, detailing Company name, Email, Address, and Phone number for each Company name Safalo, Nintex, and Drawloop.
-
For Default value, if relevant, update the provided default value.
-
For Component workflowsA workflow that can be started from outside the tenancy; the workflow uses the "Component workflow" start event.: To mark the variable as a workflow outputVariable to store a value or file on completion of the workflow. Set up as a user-defined variable., select the Output check box.
For more information about these fields, see Toolbar.
- Click Create & insert.
The Insert variables panel appears.
Note: The Create variable button is available only if you have previously created a variable.
The Create variable dialog box appears.
The new variable appears in the configuration field.
-

-
Click Variables.
The Variables panel appears, displaying the Workflow tab that is selected by default.
-
To create a variable
- Click the Workflow tab.
- Click
Create variable.
- For Name, type the internal name you want to use.
-
For Type, select a variable type corresponding to the type of data you want to store.
Variable types
- Text: Text string (with optional default value)
- Decimal: Integer numerical with a decimal point (with optional default value)
- Integer: Integer numerical with no decimal (with optional default value)
- Boolean: Yes or No (with optional default value)
- DateTime: YYYY-MM-DD, HH:MM AM/PM (with optional default value)
- Collection: A variable that groups one or more related variables of the same type into an ordered list.
- File: Path to a file. Use this variable type to attach files to email messages. A file path must start with the root folder and end with the file name. Example: /Draft/Contracts/ACME.docx
- Object: A variable that groups several related variables of any type into a hierarchical structure. Objects can contain other Objects.
- Collection of objects: A variable that groups a list of Objects of the same variable structure into a list.
For example, a collection variable named Company name can hold a list of names, such as Safalo, Nintex, and Drawloop.
For example, an Object variable named Company can hold a list of parameters, such as Company name, Email, Address, and Phone number.
Note: Objects can't be created or modified in the Variables panel.
For example, a Collection of object variable named Company details can hold a series of objects, detailing Company name, Email, Address, and Phone number for each Company name Safalo, Nintex, and Drawloop.
-
For Default value, if relevant, update the provided default value.
-
For Component workflowsA workflow that can be started from outside the tenancy; the workflow uses the "Component workflow" start event.: To mark the variable as a workflow outputVariable to store a value or file on completion of the workflow. Set up as a user-defined variable., select the check box for Output.
For more information about these fields, see Toolbar.
- Click Create.
Note: The Create variable button is available only if you have previously created a variable.

Nintex provides start event variables for most third-party start events, such as Box - New file. If you add the provided variable, then you can use it later on in your workflow.
-
On the canvas, click Start event.
The configuration panel for Start event appears.
-
From the Start from drop-down box, select a connector.
-
From the Event drop-down box that appears, select an event.
The Source section appears.
Note: The Source section is available only for some events.
- Click
Add variables.
- Select the predefined variables that you want to add to your workflow.
Note:
To select all variables, click Select All.
If you know the variable and you want to find it faster, type the variable name in the Filter options field.
-
Click Add.
The Variables dialog box appears, displaying the variables you have selected.
Note: If you want to edit the selection of variables, hover over the variable, click
, and then click Show Details. Edit the variable name in the Name field or click
.
A drop-down list appears, displaying a list of provided variables.

The Nintex - Component workflow start event allows you to create your own start event variables in the Start event configuration panel. You can use these variables to capture required workflow inputs (files or other data needed to start the workflow).
-
On the canvas, click Start event.
The configuration panel for Start event appears.
-
From the Start from drop-down box, select Component workflow.
The Start event variables section appears.
- Click
Create variable.
- Click
Create.
- For Name, enter a user-friendly name for the new variable.
-
For Type, select the variable type you want.
Data types of variables
Variable type
Usage
Text String value, such as John. Decimal Decimal value, such as 1.2. Integer
Integer value, such as 1.
Boolean
Boolean value (Yes or No).
DateTime
Date or date and time value.
Collection
Set of files or array of values. If using for file inputs, make sure your default file location is configured.
File
File. Make sure your default file location is configured.
-
Click Create.

The Variables dialog box appears, displaying the Start event tab that is selected by default.
Note: The Create button is available only if you have previously created a variable.
The Create variable box appears.
Configure the Branch by value action
In the Designer page:
-
Click the Logic and flow action group in the action toolbox.
or
Find actions by browsing action groups or by typing an action name or function in the Search field at the top of the action toolbox.
- Drag the Branch by value action to the point where you want to create multiple paths in the workflow.
- Click the Branch by value action.
- In the Variable to evaluate field, select the variable that the workflow will use to decide which branch to take.
- In the Branches fields, type the value the variable must match for the workflow to choose that branch.
-
Click the Add new branch.
- Type the value of the variable in the Name field of the new branch.
- In the Default branch field, select the branch to use if the variable does not match any branch name.
Note: The branch names must exactly match the variable value, including case.

Tip: create a branch and name it "Exceptions". Select it for your default branch. This branch will run when the action encounters unexpected data.
For more information on the fields and buttons, see Branch by value action fields, buttons, and settings

Field |
Description |
Variable types |
---|---|---|
Variable to evaluate |
The text variable that controls the branch decision. When the workflow reaches the Branch by value action, the value of this variable determines which branch is taken. |
Text, Integer |
Default branch |
The branch the workflow chooses if the variable value does not match the names of any branches. |
(n/a) |
Branches |
The names of each branch in the workflow. For a branch to be selected, the name must match the variable value exactly. |
(n/a) |
Add new branch |
Click to add another branch to the workflow. |
(n/a) |
|
Removes the branch. Note: Removing a branch also removes all the actions contained within the branch. |
(n/a) |