When Reply can't use the text of an email step or template, the editor shows an error. Here is what each error means and how to fix it.
Using of <> symbols is not allowed in the template body due to the security reasons
Reply blocks text in angle brackets that looks like an HTML tag, for example <name>, <company> or <!-- note -->. This applies to text you type and to text you paste from another tool.
To fix it, remove the angle brackets:
- for a value Reply should fill in, use a variable, for example
{{FirstName}}; - for a placeholder you will replace by hand, use square brackets, for example
[name].
Unrecognized variables found
Reply shows this when the text has something in double curly brackets that isn't a variable name. The error lists what Reply didn't recognize.
To fix it, use {{ }} only for variables, as listed in What are variables. For a placeholder, use square brackets instead, like [placeholder].
Template contains an unknown variable
The text uses a variable Reply doesn't know. Check its spelling against the variables in What are variables, and check that a custom field you use still exists.
Template can not be parsed
Reply couldn't read a variable. Possible reasons:
- a
}}without a matching{{; - empty brackets
{{}}; - symbols inside
{{ }}that a variable can't contain.
Number of starting {{ symbols does not equal the number of ending }} symbols
A variable is missing an opening or closing pair of brackets, for example {{FirstName} or FirstName}}. Add the missing brackets so every variable looks like {{FirstName}}.
Error in Body field: Email body cannot be empty
The email step has no text. Add the email text before you save.
Read more about variables: