Workflows
Workflow variables and data mapping
Insert system, context, contact, custom, and node outputs with Yanola's {{variable.path}} syntax.
Automation buildersIntermediateAvailable
What this guide covers
- Variables carry trigger data and node results into later configuration fields.
- Prerequisites: The source variable must exist on the execution path before the consuming node runs.
- Result: Test results show the expected resolved value and later nodes receive it.
- Limit: Static field labels do not guarantee every field accepts variables; use fields that expose the variable picker or say variables are supported.
What this is and when to use it
Variables carry trigger data and node results into later configuration fields.
| Use it when | Expected outcome |
|---|---|
A message, condition, integration, or action needs dynamic data. | Test results show the expected resolved value and later nodes receive it. |
You need a value from an earlier node. | Test results show the expected resolved value and later nodes receive it. |
Before you begin
- The source variable must exist on the execution path before the consuming node runs.
Prerequisites
The source variable must exist on the execution path before the consuming node runs.
Complete the task
- Open Variables from the workflow canvas.
- Choose System, Context, Contact, Custom, or Nodes.
- Select a variable to copy it.
- Insert it into a variable-aware field such as {{contact.name}}.
- For Set Variable, use a valid name and read it later as {{custom.name}}.
- Run Test and inspect output variables at each step.
Confirm it worked
- Test results show the expected resolved value and later nodes receive it.
Common problems
| Symptom | What to check |
|---|---|
Variable renders empty | Verify its source node ran on that branch and the key is exact. |
Custom name is rejected | Start with a letter or underscore and use only letters, numbers, and underscores. |
Current limitations
Static field labels do not guarantee every field accepts variables; use fields that expose the variable picker or say variables are supported.
Product boundary
Static field labels do not guarantee every field accepts variables; use fields that expose the variable picker or say variables are supported.
Where to go next
Related documentation
Set VariableStore a value for later use. Exact configuration, outputs, execution behavior, errors, limits, and examples for the Set Variable workflow node.Variables contain unexpected valuesCheck variable scope, exact path, trigger context, execution branch, preceding node output, and value type.Test a workflowRun a saved workflow with test contact and trigger data while preventing message, database, and external side effects.