Reuse an answer later in the flow
Name an answer with an identifier, then print it back on a later screen, put it in an email, or test it in a condition.
Every answer is stored under a name you choose. Write that name with a $ in
front of it and Tayon replaces it with the answer.
Ask What is your name? with the identifier NAME, and a later screen that
says Thanks $NAME, here is what we found shows Thanks Maya, here is what we
found.
#Name the answer
The name is the Identifier (Variable Name) on a screen’s Interaction tab.
- Open the screen that asks the question.
- On the Interaction tab, set Identifier (Variable Name).
- Use it later as
$plus that name.
Rules of thumb:
- Uppercase, no spaces:
NAME,EMAIL,COMPANY_SIZE. Variables are matched exactly as written, so$nameis not the same as$NAME. - Short. You will type it a lot.
- Descriptive.
Q4tells nobody anything six months from now. - Unique per flow. Two questions sharing an identifier means the second answer overwrites the first.
- Not the start of another one. With both
PLANandPLAN_PRICEin a flow,$PLAN_PRICEcan come out as the plan’s answer followed by_PRICE. Use names likePLANandPRICEinstead.
Actions can store a result under an identifier too. API/Webhook Call and
AI Prompt both have a Store Response In (Identifier) field, and what
they get back is then available as $ plus that name, the same way an answer
is.
#Where you can use them
| Place | Example |
|---|---|
| Screen text | Thanks $NAME |
| Email subject and body | New enquiry from $NAME at $COMPANY |
| SMS and WhatsApp messages | Hi $NAME, your quote is ready |
| Split conditions | $BUDGET > 5000 |
| Redirect URLs | https://example.com/thanks?name=$NAME |
| Webhook parameters and headers | email=$EMAIL |
| AI Prompt text | Summarise this request: $DETAILS |
| Dataset filters and updates | STATUS=Confirmed |
Anywhere a variable is accepted, the field usually says so. The message boxes carry the reminder Use $IDENTIFIER to include collected data.
#Variables you get for free
You do not have to collect everything yourself. Tayon also fills in variables
about the visit, the contact, your account, a booking, a payment and more:
$CRMDATA.CITY prints the city on the contact’s record, $UTM_CAMPAIGN the
campaign that brought the visitor, and $FLOWASSIGNED.FNAME the first name of
the team member handling the lead.
Every one of them, and where each one works, is listed in the variable reference.
#Doing arithmetic and formatting
Formulas such as FLOW.CALCULATE and FLOW.FORMATNUMBER work out sums and
format numbers and dates, and you can pull single values out of a JSON reply.
A quote screen can read:
Your annual total is FLOW.FORMATNUMBER(FLOW.CALCULATE($MONTHLY * 12, 2), DECIMALUS)
See Formulas and JSON values for every formula and format.
#When a variable prints as nothing
Almost always one of these:
- The question comes later than the screen using it. Variables only hold what has already been answered.
- The identifier does not match. A typo produces an empty value silently. There is no error.
- The visitor skipped it. An optional question that was left blank has nothing to print.
If you see the variable itself printed, such as a literal $PLAN on the
screen, no step in this flow declares that identifier. Check the spelling
against the Identifier (Variable Name) you set.
Updated: