website logo
⌘K
Introduction
PORTAL
Agency Whitelabelling
PAGES
Pages - Accessing Page Data
Pagination Layouts
Page Templates
FORMS
Form Confirmation Pages
Adding a Progress Bar
Adding Custom CSS To Show Form Submit Process
Dynamic Content in Workflow and Autoresponder Emails
How to output Custom Field Set fields in a Form's Custom Layout
Custom JavaScript Validation for Forms
File Upload Previews
FAQ
CATEGORIES
Filtering WebApps and Modules by Categories
Outputting Categories on WebApp / Module / eCommerce Layouts
Outputting Category Fields in any Location
Category Detail Layouts
FAQ
COMPANY INFORMATION
Company Information
SITE SEARCH
Site Search
PUBLIC API/ZAPIER
Zapier - Formatting arrays correctly
Public API/Zapier Changelog
MODULES
Module Marketplace
Building Custom Modules
Siteglide Modules
Front-end Submit Modules
DATA STRUCTURES
Automations
Creating WebApps from the CLI
Field Types
WEBAPPS
Front-end Submit WebApps
Layouts
Search and Filtering
Understanding Custom Field Names and IDs
FAQ
CRM
User Details
User Secure Zones
Storing User's Favourite WebApp / Module Items
User's Form Submissions (Cases)
How Users Edit their Email and Password Front End
Editing a User's CRM record Front End with Custom Field Sets
CLI
Introducing Siteglide CLI
CLI Changelog
Secure Zones with CLI
Page Templates with Siteglide CLI
Pages with Siteglide CLI
Includes with Siteglide CLI
Managing Email Templates
Migrate - Manual Form setup
Migrate - Convert existing Forms
Liquid
Accessing Assets
Liquid Dot Notation
Using WebApp Collections- Tutorial
Using the current_user object with Secure Zones
Preventing Duplicate Content with Query Parameters- Canonical URL and Robots.txt
FAQ
GraphQL
Tutorial Overview
About GraphQL
Tutorial 1- Your First Query
Tutorial 2 - Pagination
Tutorial 3 - Filtering the Results
Tutorial 3 - Answers to the First Filtering Challenge
Tutorial 4 - Advanced Filtering
Tutorial 4 - Challenge Answers
Tutorial 5 - Using Liquid to run GraphQL queries on your Site
Tutorial 6 - Variables
Tutorial 6 - Answers to the Variables Challenge
Tutorial 7 - Sorting
Tutorial 8 - Building a Liquid API GET Endpoint Page powered by GraphQL queries
Best Practice and Performance
Module/WebApp Caching
Getting Started with Liquid Caching - to Reduce Server Response time and Improve Performance
Includes
ecommerce/checkout_standard
Frequently Asked Questions
Using Liquid Logic to Check if a field exists, or is empty on the Front End
How do I learn more about Liquid?
How to setup a multi domain start page
Docs powered by archbee 
12min

Dynamic Content in Workflow and Autoresponder Emails

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.

Document image

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. 

Document image

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:

HTML
|

In the Email:

HTML
|

Related Articles

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

Updated 19 Oct 2021
Did this page help you?
Yes
No
UP NEXT
How to output Custom Field Set fields in a Form's Custom Layout
Docs powered by archbee 
TABLE OF CONTENTS
Introduction
Outputting Form Fields - submitted in the Form which triggered the Email
Outputting WebApp and Module Data in the Email
Outputting a Specific WebApp Item in an Email
Related Articles