Emails

Workflow Emails

Here you can create additional custom Workflow Notification emails, beyond the single default email, that can be assigned to Workflows. This provides more flexibility with the email notifications you send out to site admins / team members.

For example; you may want to send differently branded or styled emails to certain departments or teams since they may have different requirements and need different types of data displayed.

Custom Workflow Emails are available for PRO plans and above.

You can create any number of custom Workflow Emails and they’ll be displayed in the table where you can further search, edit or delete those emails.

Apart from giving the email a descriptive name, editing options for custom Workflow Emails are the same as for the default Workflow Email (found in the ‘System Emails’ section). More information on these fields can be found here.

Dynamic content can be added to the email body, rendering information from the form submission, workflow and the CRM contact, as well as inserting most other Liquid components and logic (suitable for email content).

For example; you could render information about the Form Submission directly from the this.formSubmissionData Liquid object, or information about the customer via the this.member object.

Some Sample Data

To render the name of the Form:

{{ this.formSubmissionData['form_name'] }}

My Enquiry Form

For more information about rendering Form Submission data, including looping through all the form fields, see the Form Submission object documentation here.

To render the name of the Workflow being used:

{{ this.workflow['name'] }}

Enquiry Workflow

For more information about rendering Workflow data see the documentation here.

To render the contact's first name:

{{ this.member['firstname'] }}

Alex

Once you’ve created your Workflow Email you can assign it to a Workflow via the Workflow edit screen. You can also create these Workflow Emails directly from the Workflow edit screen for a more streamlined creation process.

Follow-up Emails

Here you can create your emails for Event reminder/follow-up notifications to the registered user. This allows you to build customised emails for any stage of the Event process that you define via the Event edit screen.

You can create any number of Event follow-up emails and they’ll be displayed in the table where you can further search, edit or delete those emails.

Apart from giving the email a descriptive name, editing options for the emails are the same as for most system emails (found in the ‘System Emails’ section). More information on these fields can be found here.

Dynamic content can be added to the email body, rendering information from the Event and the CRM contact, as well as inserting most other Liquid components and logic (suitable for email content).

For example; you could render information about the Event directly from the this Liquid object, or information about the contact via the this.member object.

Some Sample Data

To render the name of the Event:

{{ this['Name'] }}

My Event Name

To render the start date of the Event (with date formating)

{{ this['EventDateStart'] | date: "%e %b %Y at %l:%M%p" }}

4 Jan 2023 at 4:30PM

To render the contact's first name:

{{ this.member['firstname'] }}

Alex

Once you’ve created your reminder/follow-up email you can assign it to a notification rule via the Event edit screen

Abandoned Cart Emails

Here you can create your emails for the Abandoned Cart notifications to the user. This allows you to build customised emails for any stage of the Abandoned Cart process that you define via the Abandoned Cart interface.

Abandoned Cart functionality is available for ECOMMERCE plans via the Abandoned Cart extension.

You can create any number of Abandoned Cart emails and they’ll be displayed in the table where you can further search, edit or delete those emails.

Apart from giving the email a descriptive name, editing options for the emails are the same as for most system emails (found in the ‘System Emails’ section). More information on these fields can be found here.

Dynamic content can be added to the email body, rendering information from the Shopping Cart and the CRM contact, as well as inserting most other Liquid components and logic (suitable for email content).

Also available in these emails are the this.TrackingURL and this.RestoreCartURL which provide a 1px X 1px tracking image and a link for the customer to restore their cart session.
The tracking pixel will be added automatically to the email while the Restore Cart link would need to be added within your email content.

For example; you could render information about the cart and products via the this.ShoppingCart Liquid object, or information about the customer via the this.member object and provide a link for the customer to restore/view their abandoned shopping cart.

Some Sample Data

To render the total items count:

{{ this.ShoppingCart.TotalItemsCount }}

3

For more information about rendering Product data, including looping through all the Product line items, see the Shopping Cart object documentation here.

To render the contact's first name:

{{ this.member['firstname'] }}

Alex

For more information about rendering Member data, see the Member object documentation here.

Rendering the tracking pixel image:

<img src="{{this.trackingURL}}" height="1" width="1">

This tracking pixel will be added to your emails automatically. You do not need to manually add this.

To render the Restore Cart link:

{{this.RestoreCartURL}}

https://[siteDomain]/public/api/track-email/abandoned-cart/open?id=[ShoppingCartid]&notificationId=[idOfAbandonedCartNotificationStep]&guid=[guid]

Once you’ve created your Abandoned Cart email you can assign it to a notification rule via the Abandoned Cart extension interface.

Email Domain Authentication

All system emails (ie: Workflow Notifications, Autoresponders, Follow-up Emails, Abandon Cart Emails, etc.) can be reliably sent out via the system email domain of trustedemail.co (so a “From” email address can be used for system emails with any username, such as admin@trustedemail.co).

If you wish to use your own custom domain email address for sending out system emails you can do so also. Just be sure to authenticate your email domain with SPF and DKIM authentication methods as detailed in the following documentation articles:

• Email Domain Authentication (DKIM)
• SPF Authentication

Related Articles

• Email Notifications
  Workflows
  A Workflow is an action (or rule) that determines how a notification is handled. Workflows allow for greater control of email notifications that get sent when Forms are submitted on the front-end of your website. In this case we’re looking at Email Notifications.
• Email Notifications
  Email Templates
  Email Templates provide a top-level wrapper for one or more of your system email’s contents, allowing for consistent branding and styling across emails sent via the CMS (such as Workflows, Autoresponders, reminders, follow-ups, abandon cart emails, etc.).
• Email Notifications
  System Emails
  System emails are emails that are sent when a particular action is carried out on the website and/or via the admin.
• Liquid Objects & Usage
  {{ member }} object
  This liquid object will output the Member's details of whom submitted a Form. You can...
• Liquid Objects & Usage
  {{ workflow }} object
  This liquid object will output the Workflow details of a submitted Form. You can use...

External Resources

There are currently no external resources available.

Please let us know if you have any other contributions or know of any helpful resources you'd like to see added here.

Questions?

We are always happy to help with any questions you may have.
Visit the Treepl Forum for community support and to search previously asked questions or send us a message at support@treepl.co and we will consult you as soon as possible.