Troubleshooting
Variables contain unexpected values
Check variable scope, exact path, trigger context, execution branch, preceding node output, and value type.
Automation buildersBeginnerAvailable
What this guide covers
- Variables reflect the current execution and only outputs from nodes that ran earlier on the selected path.
- Prerequisites: The exact variable expression and a representative execution/test input.
- Result: Test resolves the intended value for every important branch.
- Limit: Not every trigger supplies message, contact, conversation, media, keyword, interactive, or location context.
What this is and when to use it
Variables reflect the current execution and only outputs from nodes that ran earlier on the selected path.
| Use it when | Expected outcome |
|---|---|
A message, condition, AI prompt, or integration receives empty or incorrect dynamic data. | Test resolves the intended value for every important branch. |
Before you begin
- The exact variable expression and a representative execution/test input.
Prerequisites
The exact variable expression and a representative execution/test input.
Complete the task
- Copy the key from Variables instead of typing from memory.
- Verify the prefix: system, context, contact, custom, or nodes.
- Confirm its source exists for the trigger type.
- Confirm the producing node ran before the consuming node on the same branch.
- Inspect Test output variables and data type.
- Add a Condition or fallback for optional values.
Confirm it worked
- Test resolves the intended value for every important branch.
Common problems
| Symptom | What to check |
|---|---|
nodes output is absent | The source node was skipped, failed, or is downstream. |
contact value is absent on Scheduled/Webhook | Provide explicit data because there is no inbound conversation context. |
Current limitations
Not every trigger supplies message, contact, conversation, media, keyword, interactive, or location context.
Product boundary
Not every trigger supplies message, contact, conversation, media, keyword, interactive, or location context.
Where to go next
Related documentation
Workflow variables and data mappingInsert system, context, contact, custom, and node outputs with Yanola's {{variable.path}} syntax.Set VariableStore a value for later use. Exact configuration, outputs, execution behavior, errors, limits, and examples for the Set Variable workflow node.Test a workflowRun a saved workflow with test contact and trigger data while preventing message, database, and external side effects.