Find the exact variable (and copy it)
If you just need the essentials, follow this quick path:
- Open the flow you want to debug
- Run the Simulator and reach the step you’re investigating
- Open the Context Explorer using the “@” icon
- Expand the variable tree (contact, results, input, globals, run)
- Copy the variable/expression and paste it into nodes (messages, splits, webhooks)
This is the fastest way to understand what your flow “knows” at any point and why a branch or message behaved the way it did.
Step-by-Step Process
- Go to Flows.
- Open the flow you want to inspect.
[CAPTURE: Flow opened in the editor.]
- In the flow editor, locate the Simulator button (phone icon / simulator panel).
- Click Run in Simulator.
- Run the test contact up to the step where you want to inspect variables (you don’t always need to finish the flow).
[CAPTURE: “Run in Simulator” button / Simulator panel opened.]
- Respond to the simulated messages as needed.
- Continue until you reach the point you want to debug (or run to the exit/end).
[CAPTURE: Simulator conversation progressing through nodes.]
@results, you must run past the node that creates it (for example, a Wait for Response that saves a named result).- In the Simulator, click the “@” icon (bottom-left of the simulator).
- The Context Explorer opens and shows a structured list of all available variables.
[CAPTURE: “@” icon highlighted and Context Explorer opened.]
@input, @results, and run metadata).Inside the explorer, you can:
- Browse key sections like contact, globals, results, input, and run.
- Expand any item to see deeper details (timestamps, language, groups, fields, etc.).
- Copy the variable/expression and paste it into:
- Send Message text
- Split by Expression
- Webhook configuration
- Update Contact and other actions
Examples of what you might inspect during a test run:
- A test contact phone number under
@contact - A shared value under
@globals - The latest inbound text or attachments under
@input - Flow results collected under
@results - Run/session metadata under
@run
[CAPTURE: Expanded variable tree showing contact details, globals, results.]
Common Issues & Quick Fixes
I don’t see the “@” icon in the simulator
Problem: The Context Explorer control isn’t visible.
Fix:
- Make sure the Simulator is running (you must click Run in Simulator first).
- If the simulator panel is collapsed, expand it fully and look at the bottom-left.
My variable is empty or missing in the explorer
Problem: You expected a value, but it’s blank or not present.
Fix:
- Run the simulator past the node that creates the value (for example, a Wait for Response that sets
@results). - If it’s a contact field, confirm the flow updated it with an Update Contact action.
I copied a variable but it doesn’t work in my message
Problem: The message renders the variable text instead of a real value.
Fix:
- Confirm you copied the exact expression (including prefixes like
@contact/@results/@globals). - If you’re using variables inside expressions/functions, wrap them correctly (for example,
@(function(...))when needed). - Check for typos—invalid variables often display as plain text.