Introduction to Flow Variables

By design, a flow that incorporates Split Actions generates a set of variables from each evaluation performed. For instance, the Wait for Response action illustrated here will create the flow variable @results.phone once a contact replies and progresses to the subsequent node.

Every variable is preceded by the @ symbol, which activates an auto-complete dropdown menu displaying all accessible variables:

Once a variable type is selected, pressing the “tab” key on your keyboard will present a list of variables available within that category. In the following example, entering @results and pressing “tab” displays a list of flow values gathered within the current flow from every Wait for Response action:

 

Pressing the “enter” key enables you to define the platform-specific metadata linked to each value. As shown below:

  • value retrieves the run’s value

  • category returns the run’s category, etc.

 

When a contact is active in a flow, each variable is substituted with its corresponding value. If an invalid variable is inserted, the message will display the variable name instead.

Note: Result and field variables can store a maximum of 640 characters.