> For the complete documentation index, see [llms.txt](https://viewzenlabsug.gitbook.io/userguides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://viewzenlabsug.gitbook.io/userguides/appverse/apps/create-an-app/forms/events-and-actions/send-notifications.md).

# Send Notifications

Apps -> \<App> -> Events & actions -> Send notification

The **Send Notification Action** in **AppVerse** allows users to automatically trigger notifications, such as **SMS** or **email alerts** or **In-App notifications**, based on specific conditions.

### Key Features

* **Notifications** work on the same principles as the other Events and actions i.e.,&#x20;
  * they can be triggered manually or on form submission or on record update.
  * they can be triggered when specific conditions are met.
  * they can be executed synchronously or asynchronously .
* Notifications can be mapped in this section, but they must be **pre-configured**. For more details on how to configure notifications, refer to our **Notification Application**.

### Mapping Pre-configured Notifications / Additional Configurations

To use notifications in **Events and Actions**, they must first be pre-configured in the **Notifications Application**. Dynamic variables, which can be populated during execution, can be embedded within the template. Once configured, pre-built templates can be linked to a form’s notification event and action, where they will be dynamically populated based on the record data or other relevant details. To link pre-configured templates and their dynamic variable, follow the following steps

{% stepper %}
{% step %}
**Select Alert**

Select the relevant pre-configured notification tempate
{% endstep %}

{% step %}
**Template Variable Mappings**

Under this section, map all the dynamic variable in the template to a form field or a constant.
{% endstep %}

{% step %}
**Trigger after actions**

If this property is enabled, the notifications will get triggered only after all the other actions have been completed.
{% endstep %}
{% endstepper %}

### Examples

* **Order Confirmation:** Send an email to a customer when their order is successfully placed.
* **Task Assignment:** Notify a team member via SMS when a new task is assigned to them.

<figure><img src="https://2529980633-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK8cCKBpIeUsWEwOw3Fbj%2Fuploads%2F9x3w1Kb20OjHFEIfLIhL%2Fnotificationena.jpg?alt=media&amp;token=662b237b-6515-4c9a-9e00-0e35955bb7a3" alt=""><figcaption><p>Send notifications</p></figcaption></figure>