Notification Nodes

Last updated June 11, 2026, 2:13 PM UTC · fuuz.com/help/notification-nodes

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:

Create a Notification Channel with sendEmail: false
Use Send Notification node to publish to the channel
Create a separate flow with Receive Notification node listening on the same channel
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