> For the complete documentation index, see [llms.txt](https://waf-doc.inext.checkpoint.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://waf-doc.inext.checkpoint.com/setup-instructions/setup-notification-triggers.md).

# Setup Notification Triggers

CloudGuard WAF safeguards web servers against attacks. You can set up Trigger objects to specify actions when an event occurs. One type of Trigger object, "Notification", allows sending email notifications to multiple addresses for events related to your agents

## Setting up a Notification Trigger

#### Step 1: Create a new "Notification" trigger

Browse to **Policy -> Triggers** and create a new Trigger object of type **Notification**.

<div align="left"><figure><img src="https://2760087783-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEWA4nfgNrSRL8dA6Kap7%2Fuploads%2FWHVBx1KdJhMjBxNKMPV7%2FCapture.PNG?alt=media&amp;token=38718a07-6e48-440f-a46b-25352a8d47a7" alt=""><figcaption></figcaption></figure></div>

Configure a new name to the new trigger object:

![](https://2760087783-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEWA4nfgNrSRL8dA6Kap7%2Fuploads%2FHkfs3YG2e7E75YW4kUT4%2FCapture1.PNG?alt=media\&token=5ff4246a-4414-4b2a-90d9-cbc15f2ea70d)

#### Step 2: Configure intervals and email addresses

1. **Intervals in hours** - Specify the interval in hours for receiving notifications. You will receive an email at each set interval (e.g., every 2 hours) if any events occurred.
2. **Emails recipients** - You can choose one of the following options:
   1. **Send all admins in the tenant** - According to the Admins listed under **Account** -> **Users**.
   2. **Send all users in the tenant** - According to the list of users listed under **Account** -> **Users**.
   3. **Custom Emails -** Send to a customize list of email addresses

<div align="left"><figure><img src="https://2760087783-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEWA4nfgNrSRL8dA6Kap7%2Fuploads%2FRu71dPZ5eYzxQgNIvgQ0%2FCapture2.PNG?alt=media&amp;token=2d0d52e8-cbb7-4c24-b93f-9d4ba99849f6" alt=""><figcaption></figcaption></figure></div>

#### Step 3: Choose the Events you wish to get notified about

Select the checkboxes for events you want to be notified about. You can also choose all the events.

<figure><img src="https://2760087783-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEWA4nfgNrSRL8dA6Kap7%2Fuploads%2Fp9XlAam1b3tqrQFEKSw0%2FCapture3.PNG?alt=media&amp;token=c6d7cf80-cb2e-4208-b375-8a2417a5be20" alt=""><figcaption></figcaption></figure>

#### Step 3: Setup your Threat Prevention policy to use the new Log Trigger object/s

Browse to **Policy**->**Assets** and edit the asset you wish to modify.

Go to the **relevant practice** tab and scroll to the bottom.

![](https://2760087783-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEWA4nfgNrSRL8dA6Kap7%2Fuploads%2FRUhX5rQW2fNrogQhPLSA%2FUserResponsePage.png?alt=media\&token=c028d198-0997-4976-9ed1-d1483688bf43)

Click on the 'Add triggers' lint and add your new Notification Trigger object.

{% hint style="warning" %}
The trigger must be connected to an asset, published, and enforced to be activated.
{% endhint %}

## Notification Email Example

The screenshot below illustrates a sample notification email that you will receive after configuring the notification trigger.

<figure><img src="https://2760087783-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEWA4nfgNrSRL8dA6Kap7%2Fuploads%2FHIhpWXnwd0an7u88fuJW%2FNotificaionTriggerExample.png?alt=media&amp;token=d47dd7a3-4b5e-4071-9d04-e5e0320ce451" alt=""><figcaption></figcaption></figure>


---

# 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://waf-doc.inext.checkpoint.com/setup-instructions/setup-notification-triggers.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.
