> For the complete documentation index, see [llms.txt](https://docs.infraon.io/infinity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraon.io/infinity/user-guide/infraon-configuration/infraon-automation/notification-rule.md).

# Notification Rule

The Notification module enables you to automate notifications across different Infraon modules by defining notification rules and reusable templates. It helps ensure that users receive timely updates whenever specific events or actions occur within the selected module.

Notification configuration is organized into two tabs:

* **Notification Rules** – Define when notifications are triggered, who receives them, the delivery channels, and the delivery schedule.
* **Templates** – Create and manage reusable notification templates that define the notification subject and message content.

The Notification module supports the following modules:

* [Ticket](/infinity/user-guide/ticket-management/tickets.md)
* [Request](/infinity/user-guide/request-management/request.md)
* [Problem](/infinity/user-guide/problem-management/problem.md)
* [Change](/infinity/user-guide/change-management/change.md)
* [Release](/infinity/user-guide/release-management.md)
* [Project](/infinity/user-guide/workspace/project-management/project.md)

Select the required module from the Module drop-down to configure notification rules and templates specific to that module.

## **Rules**

The Notification Rules tab lets you create and manage automation rules that determine when notifications are generated for events in the selected module.

Each rule combines a trigger, notification template, recipients, delivery channels, conditions, and delivery schedule to automate notifications.

Using Notification Rules, you can:

* Define the event or trigger that initiates a notification.
* Associate a notification template with the rule.
* Configure notification delivery channels, such as Email and In-App notifications.
* Specify recipients based on users or roles.
* Apply conditions to control when notifications are triggered.
* Configure real-time or scheduled notification delivery.

## **Templates**

The Templates tab allows you to create and manage reusable notification templates that can be associated with notification rules. Templates define the notification subject and message content, providing a consistent communication format across multiple notifications.

Using Templates, you can:

* Organize templates by notification category.
* Configure the notification subject and message body.
* Insert supported module-specific variables (tokens) into the message body.
* Reuse templates across multiple notification rules.
* View the number of notification rules currently using each template.


---

# 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.infraon.io/infinity/user-guide/infraon-configuration/infraon-automation/notification-rule.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.