Emails are Liquid files, so they can include WebApp or Module List Views. You can also output fields that were submitted in the Form.

Introduction

Emails are Liquid files, so they can include WebApp or Module List Views. They can also include Liquid filters, logic and loops.



Outputting Form Fields - submitted in the Form which triggered the Email

Let's say you have a User fill in a form and you want to send a confirmation Email to them, wouldn't it be great to personalise it to them a little? Since they've just filled in their name and other information in the form, accessing the form submission information is extremely useful. 

To test, and find the real names of the fields you might need, output all available form submission data in a test Email with: {{form}}Use that to identify form fields that you would like to output and use dot notation to output the ones you need. 

For example, it should be possible to access the name of the User submitting the form with the following: {{form.properties.name}} Custom Fields can also be accessed here, though their database names will show instead of their user-friendly names, so its best to use the content to identify them while testing: {{form.properties.form_field_4_1}}

Outputting WebApp and Module Data in the Email

Visit the related Articles below for reference on the Liquid tags needed to output this kind of Content.  One extra thing to think about here is, what if I want to dynamically determine which item I should display in the Email?

Outputting a Specific WebApp Item in an Email

To make sure that the Email can access the dynamic ID of custom content you want to display, you can create a custom field in the Form. 



This would need to be hidden from the User, so you could add the HTML "hidden" parameter in the Form Layout (If this is not enough due to CSS rules, you may also want to wrap it in a <div> element with style="display: none". Note- the first line of the next example has been left as a generic assign (which should work on a Starter Site). You could replace the first line of the example with a ID from a more dynamic source e.g. if the form is outputted within a WebApp List Layout item.layout file, you could use this.id .

E.g. in the Form Layout:

{% assign my_dynamic_webapp_id = "98657" %}
<div style="display: none;">
  <input 
    hidden class="form-control" 
    name="{{ form_builder.fields.properties.form_field_2_1.name }}" 
    data-cfs="4-1-input_text" 
    type="text" 
    value="{{my_dynamic_webapp_id}}"
  />
</div>

In the Email:

{% assign my_dynamic_webapp_id = form.properties.form_field_2_1 %}

{%- include 'webapp'
    id: '1' 
    item_ids: my_dynamic_webapp_id
    layout: 'portfolio_2'
    per_page: '1'
    sort_type: 'properties.name'
    sort_order: 'asc' 
-%}

Related Articles

• WebApp List Layouts
• Product List Layouts
• Blog Module
• FAQs Module
• Slider Module
• Testimonials Module