Map template variables to contact fields
In the mapping rows under Preview you bind every template variable to a column on the target list, so each contact receives a value of their own.
Approved templates write their variables in double braces. Every one must point at a data source before a send. The panel offers one source: the columns of the selected target list. That column set is fixed. The project will not save while a row is left empty.
Before you start
- A selected approved template
- At least one target list selected; the sample values come from it
- The matching column filled on that list
Step by step
These screens sit inside the Intent AI section. Sign in, open Intent AI; the menu names below are in that section's left menu.
Open the mapping rows
Edit the project; the rows appear under Preview once a line and a template are set.
Read the variable's place
Each row states the variable name and its place: HEADER, BODY or FOOTER.
Pick a column for every variable
Choose the matching column from the dropdown on the right.
Check the sample values
Every option carries the sample record's value in quotes.
Watch the braces turn into values
Click the sample link; mapped variables switch to a green background.
Result checkIf it did not work
Check these
- A save that asks for a column on every parameter means one dropdown is still empty.
- A variable still in braces is either unmapped or empty on that record.
- Fill the column under Data Management, or bind the variable to a column that holds data.
- The amber WapCRM warning is not your mistake. The provider does not apply that variable yet; your mapping stays saved.
Does this step look different in your panel?
We can review the screen and exact error text together.
This guide was checked against the product UI and code inventory on 29 August 2026.
