Variables

Steps read data from the run they are in. Anywhere a field says it accepts {{variables}}, type one, or click Insert variable and pick it from the list. The list only ever offers what actually resolves at that step.

What's available

Group Examples Where it comes from
Answers {{answers.rating}}, {{answers.message}} The intake form that triggered the run. One per question, keyed by the field key you gave it.
Form {{form.name}}, {{form.slug}} The form itself.
This run {{customer.email}}, {{customer.name}}, {{customer.domain}} The customer or lead the run is about. On a form capture from a brand-new lead, customer.email is the address they typed in.
Earlier steps {{steps.send_email.subject}}, {{steps.webhook.status}} Any earlier step on the same path. Every step gets a name automatically; see below.
General {{shop.name}}, {{app.name}}, {{first_name}} Always available, in flows and campaigns alike.

Answers need a form

{{answers.*}} only appears once the flow's trigger names which form. Open the trigger and pick one under Form. That does two things: the flow stops running for your other forms, and the editor can list that form's questions by name.

Leave it on Any form and the flow keeps running for every form in the workspace, as before. There are then no answer variables to offer, because there is no single set of questions to offer them from.

Passing data between steps

Nothing to set up. Every step is given a name when you add it, from its own type: the first Send email is send_email, the next is send_email_2. A later step reads it as {{steps.send_email.subject}}.

That name is fixed for the life of the step. It deliberately does not follow the step's position or the name you give it in Step name, because both of those change routinely, and a reference that quietly re-pointed at a different step when you inserted something above it would be worse than no reference at all.

One variable per field

A step offers its result broken into parts, not as one blob:

Step Offers
Send email subject, preview_text, to, from, from_name, reply_to, cc, bcc
Send HTTP request status, ok (yes/no for a 2xx), body
Draft with AI the drafted text
everything else a one-line summary of what it did

So {{steps.send_email.subject}} is the subject that actually went out, and {{steps.webhook.status}} is the response code.

Only what ran before

The picker offers a step only if it runs before the one you are editing on the same path. The two branches of an If / else are mutually exclusive: a run takes one or the other, so a step inside "If true" is never offered inside "Otherwise", nor to a step after the branches rejoin. A step inside an action group is offered afterwards, because a group's steps always run together.

Sending to an address from the run

Send email → Recipients → Specific email(s) accepts a variable as well as a typed address, so a step can email whoever filled the form: {{answers.work_email}}. Mix the two freely — a fixed ops address alongside the submitter's.

What the variable resolves to is checked before anything is sent. An address that does not survive that check is skipped and named in the run log, and a value carrying more than one address is rejected outright rather than quietly becoming two recipients.

Conditions read them too

An answer is a condition field: If / else → answers.rating → is less than → 3 branches on what someone typed. Same list, same names.

Earlier steps are there too, with the same per-field breakdown — branch on Send HTTP request · Response status code being 500 or more, say. Each step also offers a ran field: yes when it did its job, no when it skipped (no shop to tag, no recipient to email), and unset when the run never reached it at all. That is separate from a webhook's ok, which reports what the far end said rather than whether the step itself worked.

When a variable is blank

  • A question your form does not have (a typo in the key) renders as nothing.
  • A step you deleted renders as nothing too. Nothing warns you, so check text fields that referenced a step before you remove it.
  • Anything outside these groups is left exactly as you typed it, braces and all. That is the signal you have written a name nothing owns.
  • Answers are escaped in the email body, so a submitter cannot inject markup into your email.

Testing

Test run on a form flow fills the answers from that form's most recent real submission, or from the question labels when there are none yet. The test email arrives filled in, so a wrong variable is visible before a merchant sees it.