Set Values
One place to name the values a run uses — the account, the search term, the environment.
Name the values this run uses — account, search term, environment — in one step, then reference them from later steps as {{ $Set Values.json.name }}.
Reach for it when
- A template you want to re-point at a different environment by editing one step instead of six.
- The same string appearing in three Input Text steps.
Every setting this block has. A field marked only when appears once you have chosen the mode above it — those are alternatives to each other, not extra things to fill in.
- ValuesRequiredstarts at user = qa@example.com search = wireless earbuds
One "name = value" per line. Names take letters, digits and _ (that is how you reference them). true / false / a number are stored as such; quote a value ("0731") to keep it exactly as typed. Lines starting with # are notes. Values may contain {{ }} references to earlier steps.
Write one name = value per line
Names take letters, digits and _ — that is how you reference them later. Lines starting with # are notes, and a value can itself reference an earlier step.
Set ValuesSettings ValuesRequireduser = qa@example.com search = wireless earbuds env = stagingKnow what gets stored as what
true, false and numbers are stored as those. Quote a value to keep it exactly as typed — which is how a leading zero survives.
what the step puts on the table - userqa@example.com
- retries3 → a number
- "0731"0731 → kept as text
Reference them downstream
Every later step can read them — an Input Text, a URL, a message, a condition.
Set ValuesInput TextHTTP RequestIf / Branch
- The named values, for any later step to reference.
- It is not a secret store. A password typed here travels with the workflow — use a credential field on the block that needs it.
- A name with a space or a dash cannot be referenced. Underscores only.