# Notification Types

Notification engine can create several different notifications.

### Rule Based Notifications

These types of notifications mainly created at [rules](/rules-menu.md) menu by user to track and trace  deviations, anomalies for both about data and IoT infrastructure such as offline devices.

These notifications can be sent as text, email, voice email or webhooks or APIs.

 Please see [integrations ](/integrations.md)page for more detail.

<figure><img src="/files/2bcMOALrirkaVe1C6Vs7" alt=""><figcaption><p>Typical Rule Setting to Send Email as a Notification Output</p></figcaption></figure>

These types of notifications can be created as a separate web service for enterprise users.

These types of notifications can be traced in [logs ](/logs.md)page too.

### Data Service Based Notifications

These type of notifications works mostly as a separate service and with AI models.

These notifications can be tracked like a rule based notifications and also asset fields table:

<figure><img src="/files/uZijzHEQXTqULPsz9CYO" alt=""><figcaption><p>Steam Efficiency AI Based Notification Sourced By Data Service</p></figcaption></figure>

These type of notifications acts like a standard asset field so they can be used in any field related item in widgets or reporting.

Skysens AI agents also can create notifications or write directly in to asset fields. Please see [AI page](/ai.md) for more information.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.skysens.io/notifications/notification-types.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.