Workflow node reference

Set Variable

Store a value for later use. Exact configuration, outputs, execution behavior, errors, limits, and examples for the Set Variable workflow node.

Automation buildersIntermediateAvailable

What this guide covers

Category: Logic.
Use it to save a static value, another variable, or a supported expression for later nodes.
3 configuration fields and 2 documented outputs.
Custom variables last for the current execution; they are not an account database.

What this node does

Store a value for later use

Use it to save a static value, another variable, or a supported expression for later nodes.

When not to use it

Do not use it to permanently update the contact; use Update Contact.

Prerequisites

Name beginning with a letter or underscore
Only letters, numbers, and underscores in the name
A source value available on this path

Check before configuration

Name beginning with a letter or underscore. Only letters, numbers, and underscores in the name. A source value available on this path

Inputs and configuration fields

Set Variable configuration fields
Field	Key	Control / type	Requirement	Default	Accepted values and behavior
`Variable Name`	variable_name	text	Required when shown	No default	Access later with {{custom.my_variable}}. pattern ^[a-zA-Z_][a-zA-Z0-9_]*$
`Value Type`	value_type	select	Optional	static	Static value (static), From variable (variable), Expression (expression)
`Value`	value	variable-input	Required when shown	No default	Value accepted by the displayed control. Variables supported

Configure the node

Drag Set Variable from Logic in the node palette.
Select the node to open its configuration drawer.
Complete every required field and any conditional field revealed by your choices.
Insert variables only from the current trigger or an earlier node on the same path.
Connect every required output handle to the intended next step.
Save and run Workflow Test with representative data before activation.

Outputs

Later nodes can use these values only after this node has run successfully on the same execution path.

Set Variable output variables
Variable	Type	Meaning
`{{nodes.set_variable.variable_name}}`	string	Name of the variable set
`{{nodes.set_variable.value}}`	string	The stored value

Execution behavior

Evaluates the configured source and stores it in custom scope.
Later nodes read the value as {{custom.variable_name}}.
Emits the name, value, and value type.

Retries and usage

Do not assume a failed node is automatically retried. Review the execution result and the relevant service documentation before repeating an operation that could create a duplicate side effect.

Example use case

Store a normalized priority label once and reuse it in a Slack alert and contact note.

Complete workflow pattern

text

Classifier → Set Variable → Notify Team → Add Note → End Flow

Common errors

Set Variable common errors
Symptom	Resolution
`Name is rejected`	Use ^[a-zA-Z_][a-zA-Z0-9_]*$.
`Value is empty`	Check the selected source variable or expression in Test.

Limitations

Custom variables last for the current execution; they are not an account database.

Use Update Contact for persistent profile changes.

Current product limits

Custom variables last for the current execution; they are not an account database. Use Update Contact for persistent profile changes.

Workflow variables and data mappingInsert system, context, contact, custom, and node outputs with Yanola's {{variable.path}} syntax.Update ContactUpdate contact information or custom fields. Exact configuration, outputs, execution behavior, errors, limits, and examples for the Update Contact workflow node.Variables contain unexpected valuesCheck variable scope, exact path, trigger context, execution branch, preceding node output, and value type.

Related documentation