Variables

Variables are the wiring between every part of a workflow. Understanding the namespaces and the picker is the fastest way to stop fighting the builder.

Namespaces

Inside a workflow you can reference values from several namespaces:

The old implicit {{trigger.*}} namespace is gone — trigger outputs are mapped explicitly onto workflow inputs (see Triggers).

Liquid expressions

Variable references use Liquid syntax:

{{ steps.1.account.account_name }}

{% if steps.2.health_score < 50 %}
  Flag for review
{% endif %}

The Workflow Builder Genie validates Liquid expressions, variable references, and AI output schemas as you author. Diagnostics tab errors will point at invalid references.

The variable picker

Anywhere you can type a variable, the builder offers a variable picker that shows the typed graph of available variables:

• Object fields are nested.
• Array fields (like prospects and contact_ids from Find Prospects) get a purple arr badge.
• The For Each task's Items Array picker steers you to top-level array variables — [*] sub-paths are explicitly discouraged in the hint.

Trigger → workflow mapping

When you assign a trigger to a workflow, you map each trigger output onto a named workflow input variable. The mapping is visible in the Triggers / Inputs / Outputs panel on the workflow canvas. There's no implicit pass-through.

Workflow → workflow mapping (nested workflows and For Each)

When you call another workflow via the Nested Workflow task or the For Each task, you map the calling workflow's variables onto the called workflow's declared inputs. The called workflow's outputs come back as that task's outputs.

See also

• Workflows — the I/O panel and the builder.
• Tasks — what each task type contributes to the variable graph.