Variables

Add a variable

1. Open Variables.As a workspace owner or administrator, open Variables and confirm the selected business.
2. Name it.Give the setting a unique name, such as support_url. Start with a letter or an underscore and use only letters, numbers, and underscores, up to 64 characters. A name cannot be changed later.
3. Add its value and choose Add variable.Values are text of up to 2,000 characters.

A business can keep up to 500 variables. To change a value, choose Change beside it and then Save value.

Use a variable

To use a variable named support_url, enter {{ variables.support_url }} in a workflow field. You can also put it inside text, such as Visit {{ variables.support_url }} for help., or combine it in an expression, such as {{ variables.base_url + '/v1/' + variables.region }}.

Keep the name's spelling and capitalization exact. A variable's value is always text, including values that look like numbers or true and false. To fall back when a variable is not set, write {{ variables.team ?? 'support' }}.

Variables are visible to admins and can appear in run output. Do not store API keys, passwords, or tokens here. Keep them in Secrets, or in Connections for an app's credentials.

Know when a change takes effect

NodeHub captures variables when a run starts. Changing a value affects new runs. A run that resumes or retries keeps the values it captured, so a setting does not change partway through that run.

After saving a change, start a new run and check its result. Earlier runs are not a test of the new value.

Replace or delete a variable

A name cannot be changed. To use a new name, add a variable with it, update the workflows that read the old one, and then delete the old one. New runs of a workflow that reads a deleted variable fail, unless the field gives a fallback with ??. Runs that already captured the value keep it.

If saving reports that the variable changed, refresh the list before editing again. This keeps an older edit from silently replacing someone else's change.