The Notification node sends an in-app (and email) notification to people from inside an automation — to flag that something needs attention, confirm an action, or surface an alert. Use it for approvals, status updates, and exception alerts that should reach a person rather than just sit in a log.
Overview
You address a notification to one or more users or to a user group, supply a message (often from a reusable template), and optionally attach a call to action so the recipient can act directly from the notification. The node dispatches the notification and the automation continues without waiting for it to be read.
Send Notification
Recipients
Input Field | Description |
|---|---|
Recipients — Users | One or more individual users to notify. Accepts user IDs or references resolved at runtime. |
Recipients — User Group | A user group whose members all receive the notification. An alternative to listing users individually. |
Message
Input Field | Description |
|---|---|
Template | A reusable notification template that defines the message body and subject. Recommended for consistent, maintainable messaging. |
Message (inline) | An ad-hoc message body when a template is not used. |
Call to Action — An optional action button attached to the notification so the recipient can act immediately. Choose one of the following action types:
Action Type | Description |
|---|---|
Go to page | Opens a specific page within a UnifyApps app when the recipient taps the notification. |
Open URL | Opens an external or internal URL in the browser. |
Emit page event | Fires an event in the app that a screen can listen and react to — for tightly coupled in-app workflows. |
Output: The node dispatches the notification and returns a confirmation that it was queued. No recipient-read status is returned.
Notes
Keep these behaviors in mind when using the Notification node:
Delivery is asynchronous. The automation sends the notification and moves on immediately. Do not build logic that assumes the recipient has already seen or acted on the notification.
Addressing a user group reaches all current members of that group. The membership is resolved at send time, not at automation design time.
The Emit page event call-to-action is only meaningful when the recipient has the relevant app page open; design your app screens to handle the event gracefully if it arrives unexpectedly.
Use the Notification node when you need to formally alert people with an optional action. For posting into a live chat thread, use the Chat node instead.
Understanding the asynchronous nature of notification delivery is the key to building reliable alert flows with this node.