# Custom Notifications

In Jet any action that's executed comes with the notification pop-up window, displaying different messages depending on the outcome. The typical success message looks like this:

![](/files/-MW4CDYqY2pt_w1O9ZSz)

Now you can set your own custom messaging so that our example message might be something like that:

![](/files/-MW4E-L8tV1AOUChiBXy)

### Notification types

We provide 4 types of notifications: **success**, **info**, **warning,** and **error**. You can set up any of these depending on your workflow. Let's look at the two most common use cases with Success and Error notifications.

![](/files/-MW4q_Xh1KRq26Qg3VWv)

### Set up Success notification

Let's look at the workflow of changing a customer's status, for which you have already configured a primary [action ](/user-guide/design-and-structure/actions.md)to change the status field in your data source. Now you have to set another action that'll be executed after completing the primary action (status change). The succession of events will be this:

1. Go to **After Completion** section
2. Navigate to **When action succeeded** and click **Success action**
3. Select from the dropdown **Show notification** and specify: **title**, **description**, **Success type**

![](/files/-MW4oszxjs-Cw4qu9CkG)

Now, whenever the Update button is clicked, users will see the new custom "Status Updated" notification.

### Set up Error notification

Let's consider a case where there's an error after executing an action. Error notifications in Jet usually show up with "404 or 500 status", which might be confusing to the non-tech support team. To customize our **Error notification**, we will follow the same logic as in the previous case:

1. Go to **After Completion** section
2. Navigate to **When action failed** and click **Error action**
3. Select from the dropdown **Show notification** and specify: **title**, **description**, **Success type**

![](/files/-MW521n6VwBcgy_JH3dZ)

Now, whenever there is an error in the process of executing the action, users will see the new custom "Error occured" notification.

![](/files/-MW52poy-tm-c11b6yQV)


---

# 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.jetadmin.io/user-guide/design-and-structure/components/custom-notifications.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.