Value Store
Account Values, overwrites, built-ins, and which source wins when names match.
The Value Store holds named data your Flows can read with $. Create shared Values under Assets → Values, overwrite them for a Run, and capture more data during the Test Case with Data Test Steps.
For a Flow Builder walkthrough, see Share data with Values. For test data, API setup, and mock servers, see Test data in DoesQA.
Value types
String
"https://staging.example.com", "Jane"
Number
42, 3.14
Boolean
true, false
Object
{ "id": 123, "name": "Sample" }
Use a Value in a step
In supported fields, type $ to open dynamic values. Pick an account Value by Title, or a built-in Value such as $testEmail or $randomNumber.
Which Value wins
When several sources set the same name, later sources replace earlier ones for that name.
When the Run starts
1 (base)
Account Values
Assets → Values
2
CI/CD query Values
Webhook values query parameter
3
Recipe overwrites
Settings → Run Recipes → Value Overwrites
4 (highest at start)
This-run Values
Start Run → Value Overwrites, DoesQA Run Values, or CI/CD request body Values
Schedules use the Recipe they point at, including that Recipe’s overwrites.
A rerun from Run Changed & Failed Tests keeps the Values resolved for the original Run. It does not re-read Assets → Values. Start a new Run when you need updated Values.
During the Test Case
After the Run starts:
Built-in Values apply for their reserved names (for example
$testEmailand$runLabel).Data Test Steps that store or set a key update that key for the rest of the Test Case. Those writes win for the keys they change.
On-demand built-ins such as $randomNumber only fill a name when nothing else has set it yet.
Private Values
Turn on Private value when you create a Value if the content should stay hidden in the UI after save. Private Values still apply when Tests run. You cannot view or edit the content again after save.
Related
Last updated