Notification node¶
Status: Current | Last reviewed: 2026-07-07
Sends a message via an integrated channel such as SMS or email.
Behavior¶
Template strings in recipient, message_body, subject, and from_address render with workflow merge fields. The integration_id on the node provides credentials for the selected delivery provider.
You can add this node from the workflow editor add-node menu when building a flow.
- For SMS, select the messaging integration first so the origination identity list can show active numbers and pools.
Configuration options¶
| Option | Required | Type | Values / default | What it controls |
|---|---|---|---|---|
Channel (channel) |
Yes | string | sms, email |
Required - the delivery channel for the notification. |
Recipient (recipient) |
Yes | string | Required - the destination address/number to deliver to (e.g. {{trigger.phone}}); supports merge templates. | |
Message body (message_body) |
Yes | string | Required - the message text to send; supports merge templates. | |
Subject (email only) (subject) |
No | string | Subject line for email notifications; supports merge templates. | |
SMS origination identity (sms_origination_identity) |
No | string | Sender identity used for SMS notifications, such as an origination number, pool, or provider sender id. | |
From address (email only) (from_address) |
No | string | From address used for email notifications; supports merge templates. | |
Template ref (template_ref) |
No | string | Optional reference to a communication_templates entry. | |
Requires approval (requires_approval) |
No | boolean | Default: false | When true, the send is gated behind an approval step before the message is delivered. |
Outputs¶
| Output | Type | What it contains |
|---|---|---|
status |
string | |
message_id |
string | |
channel |
string | |
recipient |
string |