Variable Mapping

Variable mapping lets you pass output data from earlier steps into later steps in your workflow. The Use Step Output panel in the editor makes previous step outputs browsable and draggable no need to manually write long path expressions.

When a step is selected in the workflow editor, the Use Step Output panel appears in the right sidebar. It lists all previous steps that are accessible from the selected step, along with their output data as an expandable tree.

From the panel you can:

• Browse nested fields inside any previous step's output
• Drag a field directly into a JavaScript or Python code editor
• Copy a field's path to use manually in expressions or text inputs

1. Select a step in the workflow canvas.
2. In the right panel, scroll to Use Step Output and toggle on Show Output Paths.
3. Expand any previous step to browse its output fields.
4. Drag a field into a code editor, or click Copy path to copy it to your clipboard.

Each step's output is rendered as an expandable tree of objects, arrays, and primitive values.

If a step hasn't been run recently, the panel falls back to a predefined schema so you can still see the expected output structure. Schema fallback is available for:

• HTTP steps — statusCode, response
• JavaScript steps — result
• Python steps — result

When both schema and actual runtime output exist, they are merged. Runtime values take precedence.

Each node in the output tree is draggable. The syntax inserted into the target editor depends on the language.

The {{ }} wrapper is stripped and the raw dot-notation path is inserted:

Path segments are converted to bracket notation:

All variable mapping paths follow this structure:

When used in text inputs or templates:

Text inputs also support:

• context — workflow execution context
• variables — workflow-level variables
• secrets — configured secrets

The panel only shows steps that are valid to reference from the currently selected step. The rules are:

• A step can reference all earlier steps in its execution path
• A step cannot reference future steps
• Inside a parallel block, each branch can only see steps from before the parallel block not sibling branches

No steps appear in the panel
The selected step is the first executable step in the workflow. No previous steps are accessible.

Output tree is empty
The previous steps haven't been run yet. Execute the process at least once to populate the output tree.

Fields are missing from the tree
The panel may be showing the schema fallback. Re-run the process to load the latest execution output.

Note: Very large or deeply nested outputs may be truncated. The tree supports a maximum depth of 12, up to 200 children per node, and up to 5,000 total nodes.