# Notifications (Alerts)

Notifications/Alerts is a crucial part of any IoT solution. Blynk offers extensive set of features to send and receive in-app (push), email, and SMS notifications from devices.

There are three main approaches you can take:

1. End-users can set up Notifications using [Automations](/en/concepts/automations.md) (if allowed so by their role and set of permissions). Once Automation is set up, Blynk.Cloud monitors the data and sends notification to the specified recipients when the condition is met.&#x20;
2. Device-driven notifications
3. [Content events](/en/blynk.console/templates/events/custom-events/events-content-events.md)

## Use Automations To Send Notifications From Blynk.Cloud (no code)

This is the easiest way of sending notifications triggered by user-defined conditions .You don't even need to write any code on the hardware, Blynk.Apps and Blynk.Console offer a simple user interface to set it up. Blynk.Cloud will do all the rest.

Read more about setting up automations here:

{% content-ref url="/pages/LvXCH7wYetNxsFRA0R7x" %}
[Automations](/en/concepts/automations.md)
{% endcontent-ref %}

## Send Notifications From Hardware

Very often notifications and alerts are an integral part of an IoT product and has to be triggered by the device itself. Blynk offers a way to pre-configure and inegrate alerts into the device logic.&#x20;

Such Notifications are part of Events functionality. You would need to configure an [Event](/en/blynk.console/templates/events.md) first

{% hint style="info" %}
Note: notifications are parts of [Events](/en/blynk.console/templates/events.md). Before moving forward:

1. Make sure your template has Event configured
2. Make sure that [Notifications are enabled](/en/blynk.console/templates/events/events-notification-settings.md) for this Event
   {% endhint %}

{% content-ref url="/pages/-MbpDjcsOSwSzuow2iXW" %}
[How to Send/Log Events](/en/blynk.console/templates/events/custom-events/events--how-to-log-events.md)
{% endcontent-ref %}

## Setting notifications for multiple devices

1. Go to [Devices](/en/blynk.console/devices.md)&#x20;
2. Select multiple devices (1)
3. Hover over the **Actions menu \[...]** (2)
4. Click **Notification Settings** (3)

<figure><img src="/files/uk9GkNCutTUPkxg0FitT" alt=""><figcaption></figcaption></figure>

In the opened drawer select the desired events to edit (4) -> **Edit Settings** (5)

<figure><img src="/files/rp4c66eIYie2QVTwlH3o" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
If the list of events is empty or you don't see the **Edit Settings** button, make sure that [Notifications are enabled](/en/blynk.console/templates/events/events-notification-settings.md) for this Event in the Device Template
{% endhint %}

<figure><img src="/files/Bqk3fgNV8tfkbXqdm845" alt=""><figcaption></figcaption></figure>

In the modal window turn on the desired channels (Email, Push, or SMS), *select the recipients*. If the recipient is not on the list you can search by typing the name or the email.

If you need to deliver notifications to all members of current organization, choose **All members** in the dropdown.

Press **Apply** and you'll see the event status and channels updated

<figure><img src="/files/JAAeiALL9llV5lq2twRR" alt=""><figcaption></figcaption></figure>


---

# 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.blynk.io/en/getting-started/notification-management.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.
