Using Templating to Customize Notifications & Confirmation Emails

Templating lets you personalize notification and confirmation messages by adding bracketed templates that are dynamically replaced with data and metadata specific to that entry. You could also think of templating as merge tags.

Templates consist of two parts: the template and the parameter. In the example below, {entry:} is the template, which tells Wufoo to pull info from entry data, and Field5 is the parameter, which tells Wufoo what exactly to pull from the entry.

Here's a template you might add to your confirmation message:

Thanks for filling out my form, {entry:Field5}!

When someone completes your form, the bracketed template in the confirmation message is replaced with their entry to Field 5—in this case, the field where they entered their first name:

Thanks for filling out my form, Beyoncé!

If there's no data to replace a template with—for example, if someone leaves a field blank—we'll just replace the bracketed template with a blank space.

Templating requires an entry to be created before you can pull data about that entry into other areas. So you can't use templating within the form itself, but instead you can use templating in several places that you or respondents see after submitting an entry to your form.

The following areas support templating:

* We suggest only using the {entry:EntryId} template in redirect URLs. You may also use any of the other templates listed below, but we advise against it since we don’t provide a way to URL encode the URL. This means if you have an unacceptable character (non-ascii or control character like a slash) in your template output, the URL will break. In other words, depending on what characters the person filling out your form enters into their response, there's a chance that it might break the redirect URL.

You can pull information into templates from lots of different data sources—answers to fields in your form, entry metadata (information about the person's entry), form metadata (information about your form), or details about someone's payment.

Data SourceTemplate


Field Data{entry:Field#}Inserts the respondent's answer to this field.

Replace # with the API ID of the field. How to find the API ID for a field »
Entry Metadata{entry:EntryId}Inserts the entry number.
{entry:DateCreated}Inserts the date and time the entry was created.
{entry:IP}Inserts the IP address of the computer that submitted the entry.
Payment Info{entry:TransactionId}Inserts the unique ID of the payment transaction.

This can only be used on payment forms using the Authorize.net or PayPal Payflow Pro merchants.
{entry:PurchaseTotal}Inserts the total amount paid (numerical value). Payment forms only.
Form Metadata{form:FormId}Inserts the unique ID of the form.
{form:Name}Inserts the Form Name.
{form:Description}Inserts the Form Description.

You can add an extra piece to your template to reformat dates and times to be clearer and more pleasant to look at.

For example, instead of displaying the answer to a Time field as 20:00:00 (the default format), you can display the time as 8:00 PM instead.

You can control the format of the date and time outputs from the following data sources:

  • Default Outputs
  • Syntax for Reformatting Dates & Times
  • Example Date & Time Templates