🇬🇧 EN

📧 Email Notification

Sends an outbound email using the SMTP server configured in Settings → SMTP Mail. Use this node to deliver automated notifications, summaries, or alerts to any email address.

Category: Notifications & Messaging · Type identifier: email_notification

Overview

The Email Notification node connects to your organisation's SMTP mail server and sends a fully formatted email at the point where it appears in your workflow. Both plain-text and HTML emails are supported. You can address multiple recipients and reference any workflow data in the subject and body using the standard {{ variable }} syntax.

Before this node can send mail, an administrator must configure SMTP credentials in Settings → SMTP Mail. If SMTP is not configured the step will fail with a configuration error.

Prerequisite: SMTP must be configured in Settings → SMTP Mail before this node can send email. Ask your administrator if you are unsure whether it has been set up.

Configuration

Field	Required	Description
To	Required	Recipient email address or addresses. Separate multiple addresses with commas. Supports `{{ variable }}`.
CC	Optional	Carbon copy recipients. Comma-separated. Supports `{{ variable }}`.
BCC	Optional	Blind carbon copy recipients. These addresses receive the email but are not visible to other recipients.
Subject	Required	The email subject line. Supports `{{ variable }}` references.
Body	Required	The email body text. Supports HTML markup and `{{ variable }}` references throughout.
Is HTML	Optional	Toggle on to render the body as HTML. When off, the body is sent as plain text. Default: off.

Output Data

On successful delivery, the node outputs the following fields:

Field	Type	Description
`sent`	boolean	`true` if the email was accepted by the SMTP server.
`message_id`	string	The unique message ID assigned by the SMTP server.
`to`	string	The resolved recipient address(es) as sent.
`subject`	string	The resolved subject line as sent.
`timestamp`	string	ISO 8601 timestamp of when the email was dispatched.

Reference output fields in later steps using {{ step_key.output.sent }}, etc.

Example Usage

The following example sends a completion summary after a data processing loop finishes. The body references the loop's counter output to include the number of records processed.

-- To field -- manager@example.com -- Subject field -- Processing complete: {{ trigger.output.job_name }} -- Body field (HTML enabled) -- Hello, The batch job {{ trigger.output.job_name }} finished successfully. Records processed: {{ counter.output.value }} Completed at: {{ loop.output.finished_at }}

Tips & Notes

Turn on Is HTML any time your body includes HTML tags such as , , or <a>. Without it, the tags will appear as literal text.
The To field can hold a variable that resolves to a comma-separated list of addresses, making it easy to send to a dynamic recipient list from a previous step.
Keep subjects short and descriptive. Many email clients truncate subjects beyond 60 characters.
If the node fails with an authentication error, ask your administrator to verify the SMTP credentials in Settings.
Delivery success means the SMTP server accepted the message. It does not guarantee the recipient's inbox received it (spam filters may still intervene).

Related Nodes

Settings: SMTP Mail — configure the outbound mail server.
Webhook Notification — send an HTTP POST notification to an external URL.
In-App Notification — create a notification inside the Flusso interface.
Slack Message — post a message to a Slack channel.