Article Type: Node Reference
Audience: Developers, App Admins
Module: Data Flows / Node Designer
Applies to Versions: Platform 3.0+
Prerequisites: Basic understanding of Data Flow concepts, Notification Channels configured
What are Notification Nodes?
Notification nodes enable sending and receiving alerts through configured Notification Channels. These channels provide centralized recipient management and can automatically send emails or be used with custom delivery mechanisms.
Why are they important?
Notification Channels decouple alert logic from recipient management. Rather than hardcoding email addresses in flows, you configure recipients once in a channel and reference that channel in your flows. This simplifies maintenance when recipients change and enables custom notification transports beyond email.
| Node | Purpose |
|---|---|
| Send Notification | Send notifications to a configured Notification Channel |
| Receive Notification | Receive messages when notifications are sent on a channel |
The Send Notification node is used to send notifications to a Notification Channel. Notification Channels are configured with recipients and can optionally send emails automatically.
| Parameter | Description |
|---|---|
| Notification Channel | Dropdown to select the channel to send notification to |
| Transform | JSONata transform - results become the payload for creating the notification message. If results are an array, multiple notifications are sent. |
sendEmail is enabled on the channel, emails are automatically sent to all configured recipientsThe Receive Notification node is used to receive messages when notifications are sent out on a notification channel.
If the sendEmail field is false on the notification channel, Fuuz will not automatically send out emails, but the Receive Notification Node will still receive the notifications. This can be used to implement custom notifications and custom transports.
| Parameter | Description |
|---|---|
| Notification Channel | The Notification Channel to receive messages for |
The Receive Notification node enables custom notification delivery beyond email:
sendEmail: falseNotification Channels are configured in the platform administration and serve as the target for Send Notification nodes. Each channel has:
| Property | Description |
|---|---|
| Name | Identifier for the channel |
| Description | Purpose of the channel |
| Binding Key | Internal routing key for the channel |
| Recipients | List of configured recipients who receive notifications |
| sendEmail | Whether to automatically send emails to recipients |
sendEmail: false and use Receive Notification for custom delivery methods| Use Notification Nodes When | Use System Email When |
|---|---|
| Recipients may change over time | Fixed recipient list (e.g., integration errors to IT) |
| Need custom delivery (SMS, Slack, etc.) | Email-only delivery is sufficient |
| Multiple flows share same recipients | One-off email with attachments |
| Need notification audit trail | Need CC/BCC/Reply-To/Attachments |
| Symptom | Likely Cause | Resolution |
|---|---|---|
| Notification emails not sent | sendEmail is false on channel | Enable sendEmail on channel or use Receive Notification for custom handling |
| No recipients received notification | No recipients configured on channel | Add recipients to the Notification Channel |
| Receive Notification not triggering | Flow not deployed or wrong channel selected | Deploy flow; verify channel matches Send Notification |
| Multiple notifications sent unexpectedly | Transform returns array | Wrap transform result in object if single notification intended |
| Version | Date | Author | Description |
|---|---|---|---|
| 1.0 | 2025-01-01 | Craig Scott | Initial release - Complete guide covering Send Notification and Receive Notification nodes with custom transport patterns. |