Skip to main content
Available starting with FlowX.AI 5.5.0The Send Notification action sends emails directly through a configured SMTP connection, without routing through Kafka.

​
Overview

The Send Notification action enables process nodes to send emails directly through a predefined SMTP connection. It supports two modes:
  • New email mode — Send a new email to specified recipients
  • Reply mode — Reply to an email that triggered the process (using data from an Email Trigger)
This differs from the existing Kafka send notification approach: instead of publishing a message to Kafka for the Notifications Plugin to process, the Send Notification action sends the email directly through an SMTP server configured as an Email Sender data source.
Notification templates configured before this feature for Kafka-based sending continue to work without modification.

​
Prerequisites

Before using the Send Notification action, ensure you have:
  1. An Email Sender data source configured in Integration Designer (or a Default Server configured at the environment level)
  2. A notification template with Email Server set to Predefined Email Connection

​
Adding the action

The Send Notification action is available on the following node types: To add the action:
  1. Select a node in your process definition
  2. Open the Actions tab
  3. Click Add action
  4. Set Action type to Send Notification

​
Configuration

​
Notification template

​
Notification Template
select
required
Select the notification template to use for the email content.
Only notification templates with Email Server set to Predefined Email Connection appear in this list.

​
Data mapping

The Data Mapping section contains the email delivery settings, starting with the reply toggle.
​
Reply to received emails
boolean
Toggle this setting to reply to the email that started the process.Default: OFF
When enabled, the reply is sent only to the original sender unless you configure CC or BCC Receivers. The subject is automatically set to RE: <original email subject>.

​
Reply mode (reply toggle ON)

When Reply to received emails is enabled, the action replies to the email that triggered the current process instance. The email is sent to the original sender, and the subject is automatically prefixed with RE:.
​
Reply to Email Header
string
required
The process variable key that contains the headerParams object from the original email received through an Email Trigger.Example: ${replyField}
The headerParams object includes the Message-ID and other headers from the original email, which are required to maintain the email conversation thread.
​
Language
string
required
The process variable key that resolves to a language code for the notification template.Examples: en, ro, fr
Use a process variable key that resolves to a language code — for example, "en" or "ro".
​
Attachments
string
Optional file attachments. Enter a file path or process variable key.
The process variable value can be a single file path or an array of file paths.
​
Receivers
string
required
The recipients for the reply. Typically references the original email sender using a process variable.Example: ${emailMessage.sender}
​
CC Receivers
string
CC recipients for the reply email. Enter emails as arrays or process variables.
If provided, these will be the only CC recipients in the email, replacing any CC recipients from the original email.
​
BCC Receivers
string
BCC recipients for the reply email. Enter emails as arrays or process variables.
If provided, these will be the only BCC recipients in the email.
​
Template Data
object
Map data sent from the process through the template. Use the JSON editor to define key-value pairs matching the data model in your notification template.

​
New email mode (reply toggle OFF)

When Reply to received emails is turned off, the action sends a new email to the specified recipients.
​
Language
string
required
The process variable key that resolves to a language code for the notification template.Examples: en, ro, fr
Use a process variable key that resolves to a language code — for example, "en" or "ro".
​
Attachments
string
Optional file attachments. Enter a file path or process variable key.
The process variable value can be a single file path or an array of file paths.
​
Receivers
string
required
The recipients for the email. Enter email addresses separated by commas, or use process variable keys.
​
CC Receivers
string
CC recipients for the email. Enter emails as arrays or process variables.
​
BCC Receivers
string
BCC recipients for the email. Enter emails as arrays or process variables.
​
Template Data
object
Map data sent from the process through the template. Use the JSON editor to define key-value pairs matching the data model in your notification template.

​
Example: Reply to a customer email

This example shows a complete flow where an incoming email triggers a process, and the process replies to the sender.
1

Set up the Email Trigger

Configure an Email Trigger data source to monitor incoming emails (for example, support@company.com).
2

Set up the Email Sender

Configure an Email Sender data source with SMTP credentials for outbound emails.
3

Create a notification template

Create a notification template for the reply email:
  1. Set Email Server to Predefined Email Connection
  2. Set Email Sender to your Email Sender data source
  3. Design the reply content using the template editor
4

Design the process

Create a process with:
  • A Message Start Event configured with the Email Trigger
  • Processing nodes for your business logic (for example, classify the email, look up customer data)
  • A node with the Send Notification action configured in reply mode
5

Configure the Send Notification action

On the appropriate node:
  1. Set Action type to Send Notification
  2. Select your notification template
  3. Toggle Reply to received emails to ON
  4. Set Reply to Email Header to the process variable containing the original email’s header params (for example, ${replyField})
  5. Set Receivers to ${emailMessage.sender}
  6. Set Language to the appropriate language code (for example, en)
When an email arrives, the process starts automatically, runs your business logic, and sends a reply to the original sender — maintaining the email conversation thread.

Email Sender

Configure SMTP connections for sending emails

Email Trigger

Configure IMAP connections to trigger processes from incoming emails

Notification Templates

Create and manage email notification templates

Node Actions

Learn about all available action types
Last modified on February 16, 2026