> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/nodes/notification.md).

# Notification

Send a platform notification to selected users from a rule chain.

<div align="left"><figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-fa33e2a8b5c07173d380bab38c72e88b3e57f773%2Frule-chain-notification-palette.png?alt=media" alt="Notification item in the Nodes palette." width="192"><figcaption><p>Notification in the palette</p></figcaption></figure></div>

Use **Notification** to send a message to selected BuildingPro Suites users when a condition is met. Its boolean **Trigger** input controls the action.

Before you begin, [open the rule chain editor](https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/open-the-configuration-of-an-existing-rule-chain.md) and identify the intended recipients. Keep the chain paused while configuring it.

<div align="left"><figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-90e49b68fe951d9a292400f6edddd162a83520fc%2Frule-chain-notification-node.png?alt=media" alt="Configured Notification node showing recipients, message, and its boolean Trigger input." width="332"><figcaption><p>Configured Notification node</p></figcaption></figure></div>

The node has one boolean Trigger input and no outputs. A false input does not send a notification.

## Configure the notification

<div data-full-width="true"><figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-43c3bd6e7889270fbd9564041460706e3ce18c9a%2Frule-chain-notification.png?alt=media" alt="Notification settings showing recipients, translated message, trigger mode, note, and Save."><figcaption><p>Notification node settings</p></figcaption></figure></div>

1. Drag **Notification** from **Nodes** onto the workspace.
2. Click the node's gear icon.
3. Select the recipients in **To** **\[A]**.
4. Enter the **Message** **\[B]** for the selected language.\
   ◈ Use the language selector and **Translation** to maintain the message in other languages.
5. Select **Trigger mode** **\[C]**:
   * **On rising edge**: Notify when Trigger changes from `false` to `true`.
   * **Always**: Notify on every execution with a true Trigger input.
6. Add a **Note** **\[D]** if needed.
7. Click **Save** **\[E]**.
8. Connect a boolean condition to the node's **Trigger** input.
9. Check the execution order and click **Save** in the editor.

{% hint style="warning" %}
With **Always**, a condition that remains true can send a notification on every chain execution. Check the chain's trigger frequency before enabling it.
{% endhint %}

After enabling the chain, check that the intended recipients can view the message in [Notifications](https://docs.buildings.ability.abb/collection/platform/platform-core/alert-and-escalation/notifications.md).

See [Trigger mode](https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/configure-rule-chain.md#trigger-mode) and the [node overview](https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/nodes.md) for related actions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/nodes/notification.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
