Page Comparison

The Email Flow Item within No Code Flows offers an automated solution for sending emails, seamlessly integrating email communication into various processes without manual intervention. Its purpose is to facilitate customized notifications based on specific conditions within workflows. For instance, in the scenario of an employee leaving a particular organizational zonelocation, the regional administrator should receive a notification, whereas in other cases, the global administrator should be notified. This flexibility send email flow item allows users to tailor email notifications to suit their unique requirements by configuring the flow item to match specific conditions.

The effectiveness of the Email Flow Item relies on can be personalized by providing the correct necessary parameters within the for workflow fulfillment in JSON. This JSON configuration enables allows users to customize email templates, specify recipient addresses, and define set conditions for email delivery. In this article, we will explore creating email templates, configuring the flow item, and defining the fulfillment workflows required for sending emails using the send email flow item.

Step 1: Create an Email Template

To send an email using the send email flow, you need to create an email template in EmpowerID. If you have already created a template, please ensure it has the necessary supported objects for the fulfillment workflows described in this section.

1. On the navbar, expand Admin, then Miscellaneous, and click Localized Emails.

2. Click the Add button above the grid to add a new template.
   

   Image Added

3. In the Email Template Details page that appears, Provide the Name, Display Name, Description, Email Body, and Email Subject fields. You can include specific objects and their properties in the Email Body and use specific object properties as email wildcards. To learn more about passing objects and using them in the email body, refer to the section Supported Email Parameters. Additionally, a sample email body is provided in the same section.
   

   Image Added

Once you've created the template, the next step would involve creating a send email flow item. But before proceeding, ensure that the email body is correctly structured and includes all necessary parameters as wildcards.

Anchor
sep sep

Supported Email Parameters

When you create an email template for a Send Email Flow Item, you have the option to use specific object parameters and convert them into wildcards. These objects are predefined, and their respective properties will be populated by the fulfillment workflows after you pass the objects. For instance, once you pass the TargetPerson Object, you can use {TargetPerson.FirstName} to insert the first name of the target person in the email template. The workflow for this flow item supports only certain objects listed below.

Email Template Samples

Below is an email template that makes use of the TargetAccount object, which is created for the onboarding person. As seen in the template, it is possible to use the properties like {TargetAccount.FriendlyName} and {TargetAccount.ExpectedHireDate} to customize the email content. Additionally, it is also possible to use custom attributes of the objects in the template.

Dear {TargetAccount.FriendlyName},

I hope this email finds you well. Please find your onboarding details.
Onboarding Details:
    Employee Type: {TargetAccount.EmployeeType}
    Hire Date: {TargetAccount.ExpectedHireDate}
    Full Name: {TargetAccount.FriendlyName}
    Preferred First Name: {TargetAccount.PreferredFirstName}
    Email: {TargetAccount.Email}
    Office Location: {TargetAccount.OfficeLocation}
    Department: {TargetAccount.Department}
    Country: {TargetAccount.Country}
    SNID: {TargetAccount.CustomAttribute10}

Your assigned email address, {TargetAccount.Email}, has been set up and activated. 

Step 2: Create Send Email Flow Item

1. On the navbar, expand Low Code and click No Code Workflows.

2. To create a flow item, click on the Flow Items tab and click the Add ​ icon.
   

   

3. Fill in the necessary details for the new flow item, including a name and any other relevant information. Make sure to select the Item Type Action, which has an item type and fulfillment workflow specifically designed for sending emails. Once all details are entered, click the Save button to create the flow item. Below is the section Supported Fulfillment Workflows that provides information about the fulfillment workflows supporting email sending for this flow item.
   

   

After creating the flow item, the next step is to add it to a flow definition. Follow the instructions below to proceed.

Step

3: Create Flow Definition & Add Flow Item

1. Click on the Flow Definitions tab and click the Add icon to proceed with creating a flow definition.
   

   

2. Provide the required information and Click Save to save the flow definition.
   

   

3. To access the View One page, click on the link to the newly created flow definition.
   

   

4. Find the Flow Items and Sequence tab and click on the add icon to add a new flow item to the sequence. “
   

   

5. To configure the send email flow item, you need to provide the necessary values and click on Save. The most important input is the fulfillment Fulfillment WF JSON, which contains parameters that customize the behavior of how the email will be sent. For it to work correctly, your parameters should consist of supported parameters or keywords.
   

   Image RemovedBelow is a sample snippet of the Fulfillment WF JSON.

   Code Block
   { "EmailTemplateName": "ManagerDeletionNotificationEmail", "EmailAddressToNotify": "dave@eidlabs.com", "DoNotSendEmailToTargetPerson": "false" }

   objects that the Supported Fulfillment Workflows support.
   

   Image Added

6. After saving the flow definition, it will appear in the list of flow items and sequences.
   

   

If you have followed all the steps in the walkthroughs provided for this section, you have successfully set up a Send Email Flow Item. When the No Code Flow is executed, the flow item will send an email according to the parameters you have configured. Please refer to the section below for supported parameters that you can use in the JSON.

Supported Parameters

When configuring the Send Email Flow Item in your workflow, you can utilize the following parameters within the Fulfillment WF JSON and the email template.

Workflow Parameters

Parameters

Anchor
sfw sfw

Supported Fulfillment Workflows

The fulfillment workflows related to the 'send email' flow item should be able to send emails and handle related parameters to ensure that the recipient receives the email as intended. The following fulfillment workflows work seamlessly with the send email flow item process.

• FWSendEmail: The FWSendEmail fulfillment workflow is designed to send emails to a Target Person. It also supports sending emails to management role members.
  In this workflow, the Business Request's target is the object being targeted in the no-code flow event. This same object is also used in the email template. For instance, in a leaver event targeting a person, the email template can utilize the 'TargetPerson' property. Additionally, the Business Request item's target resource represents the object we send an email to. For instance, when sending an email to a leaver's manager, we would use the Item Scope as 'Person's manager.'
  

• FWSendEmailToDistributionList: The FWSendEmailToDistributionList fulfillment workflow is designed to send messages to a distribution list. However, it can also send emails to management role members. The business request item’s target resource contains the object we want to display in the email template, for instance, ‘TargetPerson.’

While both are similar, certain parameters are different in the workflows; please refer to the section below for parameters.

Workflows Parameters

The fulfillment workflow supports various workflow parameters. These parameters enable you to customize your emails by specifying the recipients and the email template to be used.

Email Parameters

These are the default parameters that the email template supports. You can use these parameters while creating an email template for the send flow item. The GUID values will be replaced with the respective record names or display names.

Fulfillment WF JSON Samples

The most basic fulfillment WF JSON sample would only include the email template name, as all other parameters are optional. Please make sure to replace the parameter values with valid ones.

{
    "EmailTemplateName": "MyEmailTemplateName"
}

Below is an example of a JSON with multiple parameters. In this example, the ManagementRoleIDToNotify parameter is specified, and the DoNotSendEmailToTargetPerson parameter is set to false. This means that the email will be sent to all persons specified by the GUID of the management role. Please make sure to replace the parameter values with valid ones.

{
    "EmailTemplateName": "Test_Joiner_WelcomeEmail",
    "DoNotSendEmailToTargetPerson": "false",
    "ManagementRoleIDToNotify": "064f430e-49e5-4568-94ad-7aecd702bd79"
}