Message Node

The Message node sends an email to a recipient. Use it to notify end-users or administrators at specific points in the workflow.

The Message node selected on the Workflow Builder canvas with the Properties panel open, showing Label, Send Via, To, Cc, Bcc, From Name, Reply To, and Subject fields.

How to read settings tables

The tables below describe each configurable option as it displays in the Unqork IDE. Values are formatted as follows: inline code — a value to type exactly as shown | Bold — a value selected from a drop-down, radio button, tab, or choice chip | ON/OFF — toggle state | ✓ — checkbox checked | ☐ — checkbox unchecked

Settings

Setting	Field	Type	Default	Description
Label	`label`	Text input	`message-{n}`	A display name for the node.
Send Via	`channel`	Drop-down	—	How the message is sent. Email is the only supported option, and sends through Amazon SES.
To	`to`	Text input	—	The recipient's address. Supports template expressions (for example, `{{ data.to }}`).
↳ Cc	`cc`	Text input	—	The address to carbon copy. Visible when Email is selected.
↳ Bcc	`bcc`	Text input	—	The address to blind carbon copy. Visible when Email is selected.
↳ From Name	`fromName`	Text input	—	The display name shown as the sender. Visible when Email is selected.
↳ Reply To	`replyTo`	Text input	—	The address replies are sent to. Visible when Email is selected.
↳ Subject	`subject`	Text input	—	The email subject line. Visible when Email is selected.
Template	`template`	Module selector	—	The message template to send.
Generate and Send Refer String	`generateReferString`	Toggle	OFF	When set to ON, this setting generates a unique refer string and includes it in the message.
↳ Refer String TTL	`referStringExpiry`	Text input	`10`	The number of minutes before the refer string expires. Visible when Generate and Send Refer String is ON.
↳ Refer String Redirect Target	`redirectTarget`	Text input	—	The end-users are redirected to when they follow the refer string link. Supports template expressions (for example, `workflow/path/submission/{{ submissionId }}`). Visible when Generate and Send Refer String is ON.

Recipient Address Format

The To, Cc, and Bcc fields accept one or more email addresses separated by commas. Each field is rendered as a Nunjucks template before sending, so {{ ... }}, {% ... %}, and {# ... #} sequences are treated as template syntax and do not pass through as literal text.

Characters

Accepted characters in the local part (before the @):

Letters (A–Z, a–z), digits (0–9).
Special characters (! # $ % & ' * + - / = ? ^ _ ` { | } ~).
A dot (.) as a separator, not at the start, end, or doubled consecutively.

Domain part: letters, digits, and hyphens (not at the start or end of a label), with dots between labels. Non-ASCII domains must use Punycode encoding (for example, xn--...).

Multiple addresses and display names

Separate multiple addresses with a comma. The platform splits on every comma, so commas cannot appear inside an address or display name, even inside quotes. Whitespace around each entry is trimmed, and exact duplicates are dropped.

Display names in Name <email@example.com> format are supported, as long as the display name contains no comma. Non-ASCII characters in display names are encoded automatically.

A maximum of 50 recipients across To, Cc, and Bcc combined applies to each send. Exceeding this limit causes the node to fail.

Validation

The platform does not validate addresses at design time. An invalid address fails at send time as an SES InvalidParameterValue error, which displays in the workflow execution log.

Email Sending Limits

The Message node sends email through Amazon SES. The following AWS sending limits apply to all Unqork environments:

At 3,000 emails per day, contact a Unqork CSM to review sending volume and plan accordingly.
At 6,000 emails per day, discuss best practices and potential architectural changes with a Unqork CSM to avoid delivery issues.

These limits are enforced by AWS, not by the Unqork platform. Exceeding them might result in delayed or undelivered email.

Changelog

Date	Change
2026-08-04	Added Recipient Address Format section — characters, comma delimiter, display name format, 50-recipient cap, and runtime validation behavior (EN-7994).
—	Initial publication.