# Notification Nodes

> / Node Designer Applies to Versions: Platform 3.0+ Prerequisites: Basic understanding of Data Flow concepts, Notification Channels configured 1. Overview…

Source: https://www.fuuz.com/help/notification-nodes
Last updated: 2026-06-11

Build Apps · Data Flows


Last updated June 11, 2026, 2:13 PM UTC

## 1. Overview

**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.

### The 2 Notification Nodes

| Node | Purpose |
| --- | --- |
| **Send Notification** | Send notifications to a configured Notification Channel |
| **Receive Notification** | Receive messages when notifications are sent on a channel |

## 2. Send Notification Node

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.

### Configuration Parameters

| 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. |

### Behavior

- The transform result becomes the notification message payload
- If the transform returns an **array** , multiple notifications are sent (one per array element)
- If `sendEmail` is enabled on the channel, emails are automatically sent to all configured recipients
- Notifications are recorded in the NotificationCommunication model for audit purposes

## 3. Receive Notification Node

The 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** .

### Configuration Parameters

| Parameter | Description |
| --- | --- |
| Notification Channel | The Notification Channel to receive messages for |

### Custom Transport Pattern

The Receive Notification node enables custom notification delivery beyond email:

1. Create a Notification Channel with `sendEmail: false`
2. Use Send Notification node to publish to the channel
3. Create a separate flow with Receive Notification node listening on the same channel
4. Implement custom delivery logic (SMS, Slack, Teams, custom API, etc.)

> **Note:** *Use Case* — Send alerts to a Slack channel by receiving the notification and calling the Slack webhook API with the message payload.

## 4. Notification Channels

Notification 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 |

## 5. Best Practices

### Channel Design

- Create separate channels for different notification types (errors, alerts, reports)
- Use descriptive channel names that indicate purpose
- Manage recipients at the channel level, not in individual flows
- Document which flows use each channel

### Notification Patterns

- Use Notification Channels instead of System Email when recipients may change
- Set `sendEmail: false` and use Receive Notification for custom delivery methods
- Return arrays from Send Notification transform to batch multiple notifications
- Include relevant context in notification payload for troubleshooting

### Notification Nodes vs System Email

| 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 |

## 6. Troubleshooting

| 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 |

## 7. Related Resources

- Fuuz Platform Nodes — System Email node for direct email sending
- Source & Trigger Nodes — Event nodes (Data Changes, Topic, Publish, etc.)
- System Administration — Notification Channel configuration
- Platform Website: [fuuz.com](https://www.fuuz.com/)

## 8. Revision History

| Version | Date | Author | Description |
| --- | --- | --- | --- |
| 1.0 | 2025-01-01 | Fuuz Documentation Team | Initial release - Complete guide covering Send Notification and Receive Notification nodes with custom transport patterns. |

## See Also

- [Data Flow Nodes Reference](https://www.fuuz.com/help/data-flow-node-reference)
- [Fuuz Platform Nodes](https://www.fuuz.com/help/fuuz-platform-nodes)
- [Source & Trigger Nodes](https://www.fuuz.com/help/source-trigger-nodes)
- [Notifications](https://www.fuuz.com/help/notifications)
- [Notifications](https://www.fuuz.com/help/notifications-2)

### Need more help?

Ask the Fuuz community, or open a ticket with Fuuz support.

[Ask the community](https://www.fuuz.com/community) [Open a ticket](https://support.fuuz.com/portal/en/newticket)

On this page

[1. Overview](#1-overview)

[2. Send Notification Node](#2-send-notification-node)

[3. Receive Notification Node](#3-receive-notification-node)

[4. Notification Channels](#4-notification-channels)

[5. Best Practices](#5-best-practices)

[6. Troubleshooting](#6-troubleshooting)

[7. Related Resources](#7-related-resources)

[8. Revision History](#8-revision-history)

[See Also](#see-also)
