Introduction to Flow Variables

By default, a flow containing Split Actions contains a collection of variables resulting from each Split Action evaluation. For example, the Wait for Response action below will produce the flow variable @results.phone when a contact responds and passes through it to the next node.



Each variable starts with the @ symbol, which triggers an auto-complete drop-down menu containing a complete list of available variables:



After selecting a variable type, pressing the "tab" button on your keyboard will show a list of variables available within each variable type. In the example below, typing @results and pressing "tab" shows us a list of flow values collected within the current flow from each Wait for Response action:




Pressing "enter" on your keyboard will allow you to specify the platform-specific metadata associated with each value. In the example below: 

value returns the value of the run.

category returns the category of the run, etc.




Each variable is replaced with the value it represents when a contact is active in a flow. If you insert an invalid variable, the message will instead contain the variable name.

Note: Result or field variable will only store up to 640 characters.

Next Steps

Check out our Flow Variable Reference for a full list of variables.

Updated on: 28/08/2023