> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/classic-app-builder/design-and-structure/components/alert.md).

# Alert

A flexible message box designed to display important information to users. It supports customization options, allowing you to design the alert to fit your specific needs.

## Customization

Customization is at the heart of the Alert component. You can easily modify the appearance by adding icons and adjusting colors to match your application's theme. Optional titles provide a concise summary of the alert's purpose, enhancing user understanding. Additionally, you can incorporate links to trigger actions or queries, making the alerts interactive and actionable.

### Example Usage

{% @arcade/embed flowId="9feOd073Ehcf6Hm4qzvg" url="<https://app.arcade.software/share/9feOd073Ehcf6Hm4qzvg>" %}

{% hint style="info" %}
You can define custom actions for the Alert component to handle specific scenarios in your application, attaching them to buttons within the alert. For more details, refer to our [actions documentation](https://docs.jetadmin.io/user-guide/workflow/steps/actions).
{% endhint %}


---

# 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://docs.jetadmin.io/classic-app-builder/design-and-structure/components/alert.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.