Type @ to drop a saved answer into a flow

Writing a message in a flow meant typing {{var.something}} from memory and hoping. Now you type @ and pick from what the flow has actually saved.

What's new

• @ in any message box in the builder opens a list of the variables you can use at that exact step — the answer an earlier question saved, a value an API step pulled back, a booking reference, whatever is upstream.
• It knows where you are. The list is built by walking the flow backwards from the step you are editing, so it never offers a variable that gets set after this point.
• Your contact fields are in there too, as {{attr.…}} — the same custom fields you have set up on your contacts.

"This flow" and "Sometimes set"

Variables come in two groups, and the difference matters.

• This flow — every route to this step sets it. It will have a value.
• Sometimes set — only some routes set it. Think of a question with a time-out branch that rejoins later: a customer who never answered arrives here with nothing saved.

Both are offered. We do not hide the second group — you may well be using it on purpose, and hiding it would only send you back to typing the token by hand where nothing checks it at all.

A warning when a token would come out blank

An Auto Flows message with a token the flow cannot fill does not fail — it quietly sends the sentence with a hole in it. "Your code is ." is not a good message to receive.

So a box now shows an amber line under it when something is off, and says which of three things it is:

• Nothing earlier sets this — a typo, or a step you have since deleted.
• Only some paths set this — it will be blank on the others.
• This is not a variable a flow can use — usually {{contact.email}} or similar, copied out of a chat message. Chats and flows understand slightly different lists.

These are warnings, not errors. None of them stops you activating the flow.

One small difference from the chat box

In a chat or a template you can give a variable a fallback — "use this if it is empty". A flow does not read fallbacks, so the + button is not shown on these boxes. Had it been, the fallback would have been sent to your customer as plain text, brackets and all.