Skip to main content
All CollectionsBuild & customizeEmail notifications
How to use form fields in custom email templates
How to use form fields in custom email templates

Use form field data and variables to customize email templates sent after form submissions. Include things like names, answers, and more.

Updated over a week ago

You can pipe the submitted values to customize your custom emails. You can use variables in all sections of a custom email.

For example, you can use the submitter's name in the email subject for more engagement.

⭐ Pro tip:

Learn how to set up custom emails on your forms and surveys easily.

Variables can be basic text (for example, form title), URLs (form logo, form address), or generated data (results table).

Following is a list of variables that are currently available:

Form variables

  • form_title: Title of the form.

  • form_description: Form’s description. Note that this field may have its own styling since it’s created using WYSIWYG.

  • form_success_message: Form’s success message, since you may want to include it in the email as well.

  • form_currency: Forms currency code (ISO). For example, USD or EUR.

  • form_full_address: A URL to the form’s display page (as seen by the end-user). If you’re using subdomains or custom domains, it will be linked to your custom URL. But if you’ve embedded the form in a custom page, it won’t be linked to that page.

  • form_logo: A URL to the form’s logo if you want to show it in the email.

If you want to create a template for multiple forms, this variable group is useful. These are extremely handy, and all contain the form_ prefix.

Submitted data variables

These are the most important variables that contain the fields, the submitted data on them, the result of the calculations, and a link to the row’s edit page (accessible by the form admin).


  • field_i_title: Title of a field based on its position on the form. For example, field_2_title will be replaced by the title of the 2nd field in the form, and the 4th field’s title will replace field_4_title.

  • field_i_value: Value of a field based on its position on the form. For example, field_2_value will be replaced by the title of the 2nd field in the form, and the 4th field’s title will replace field_4_value. This value can be a simple text for most of the fields, such as a choice field, text field, etc, or a link tag for file fields.

  • field_i_url: If a field is a file field, you can use this variable. For example, if your file field is in the 3rd position of your form, you should use field_3_url. While field_3_value is an HTML tag containing the file’s URL. For any field except File fields, this value will be empty.

  • alias_title, alias_value, and alias_url: You can use these to access the fields’ data based on their alias. For example, if a short text field’s alias is first_name, I can access its title and submitted value using first_name_title and first_name_value.


  • score_value: The calculated score for the forms with Logic & calculations.

  • currency: The calculated currency for the forms with Logic & calculations.

Order data

  • order_status: The order status for the forms with payment.

  • order_code: The order code for the forms with payment.

  • payment_amount: The payment amount for the forms with payment.

Basic data

  • created_at: When was the submission created.

  • submitter_referer_address: From which address has the user submitted the form?

  • email_verification_state: Email field verification status if the form has an email verification field.

  • tracking_code: Row’s tracking code if the form is to give a tracking code to the user.

  • sumbit_time: How long (minutes) did it take for the user to submit the form.

  • response_admin_address: A URL to the response’s admin page (only accessible by the user with sufficient access).


  • user_email: Submitter’s email address if the form is receiving the user’s email on an email field.

  • results_table: Will be replaced by a pre-rendered table containing all of the fields and their submitted data.

Email subject, sender name, sender email

While using the variables for these fields, please note that only simple variables are usable for these fields.

For example, you can’t use the results_table for any of these fields.
For the sender email, you can only use either a pre-defined email value (e.g. [[email protected]](/cdn-cgi/l/email-protection) ) or any variable that will return either a valid email or an empty value. If you use any other value on this field (e.g., a variable that may return a text like John Doe), your emails will not be sent successfully. It’s highly recommended to either use a predefined value, or the user_email variable, as it will be safe to use. For the subject and sender name fields, an important note is to be cautious of the variable’s length as well. Since they are limitations for their length while sending an email, we will automatically trim any texts longer than the standard length.

The email template doesn't support the value of lookup fields.

Did this answer your question?