Send Email Notifications

Send email notifications automatically within No Code Flows by configuring Email Flow Items. Use JSON parameters to specify email templates, recipients, and delivery conditions based on workflow events.

Prerequisites

This article assumes familiarity with Flow Items and Flow Definitions. For foundational information, see:

• Create Flow Items
• Create Flow Definitions

You must also know how to create email templates in EmpowerID.

Configure Email Notifications

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.

   Figure 1: Click Add to create a new email template

3. In the Email Template Details page, enter the Name, Display Name, Description, Email Body, and Email Subject. Include object properties in the Email Body using wildcards. See Configuration Reference for supported parameters and examples.

   Figure 2: Email Template Details page with configuration fields

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

5. Click the Flow Items tab and then click the Add button.

   Figure 3: Click Add to create a new Flow Item

6. Enter the flow item details, including a name. Select the Item Type Action with a fulfillment workflow for sending emails (see Configuration Reference for supported workflows). Click Save.

   Figure 4: Flow Item configuration with Item Type Action selected

7. Click the Flow Definitions tab and click the Add button to create a flow definition.

   Figure 5: Click Add to create a new Flow Definition

8. Enter the required information and click Save.

   Figure 6: Flow Definition configuration page

9. Click the link to the newly created flow definition to access its View One page.

   Figure 7: Click the Flow Definition name to open its View One page

10. Find the Flow Items and Sequence tab and click the Add button to add a flow item to the sequence.

    Figure 8: Click Add to add a Flow Item to the sequence

11. Enter the required values including the Fulfillment WF JSON, which contains parameters that customize email sending behavior (see Configuration Reference for supported parameters and examples). Click Save.

    Figure 9: Configure Flow Item with Fulfillment WF JSON parameters

    The flow item appears in the list of flow items and sequences.

    Figure 10: Flow Item successfully added to the Flow Definition sequence

When the No Code Flow executes, the flow item will send an email according to the configured parameters.

---

Configuration Reference

Supported Email Parameters

Use these object parameters as wildcards in email templates. Properties are populated by fulfillment workflows. For example, use {TargetPerson.FirstName} to insert the target person's first name.

Parameters	Description	Example
TargetPerson	Target Person object when the event is targeting a person	{TargetPerson.FirstName}
TargetAccount	TargetAccount object when the event is targeting an account	{TargetAccount.EmployeeType}
TargetPersonManager	Manager of the target person	{TargetPersonManager.FirstName}
TargetAccountManager	Manager of the target account	{TargetAccountManager.FirstName}
TargetBusinessRequest	Business request or task object associated with the No Code Flow	{TargetBusinessRequest.Friendlyname}
TargetBusinessRequestItem	Business request item object within the business request task	{TargetBusinessRequestItem.FriendlyName}

Email Template Sample

Example template using the TargetAccount object for onboarding notifications. Custom attributes can also be used in templates.

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. 

Supported Fulfillment Workflows

FWSendEmail
Sends emails to a Target Person or management role members. The Business Request's target object is used in the email template. For example, in a leaver event targeting a person, the template uses the 'TargetPerson' property. The Business Request item's target resource represents the email recipient. To send email to a leaver's manager, set the Item Scope to 'Person's manager.'

FWSendEmailToDistributionList
Sends emails to a distribution list or management role members. The business request item's target resource is the object displayed in the email template (e.g., 'TargetPerson').

Workflow Parameters

Configure email recipients and templates using these fulfillment workflow parameters.

Parameter	Description	Optional?	Supporting Workflows
EmailTemplateName	Email template name. Ensure the template has been created with necessary parameters.	No	FWSendEmail, FWSendEmailToDistributionList
EmailAddressToNotify	Email address for notifications. Can be combined with ManagementRoleIDToNotify to send to both the specified recipient and management role members.	Yes	FWSendEmailToDistributionList
DoNotSendEmailToTargetPerson	When true, email will not be sent to the target person (Business Request's target resource). Typically used when sending email to management role members instead of the target person.	Yes	FWSendEmail
ManagementRoleIDToNotify	GUID of a management role. Email will be sent to all members in the role.	Yes	FWSendEmail, FWSendEmailToDistributionList

Fulfillment WF JSON Samples

Basic configuration with required email template name only:

{
    "EmailTemplateName": "MyEmailTemplateName"
}

Configuration with multiple parameters:

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

Replace parameter values with valid ones for your environment.