> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/component-builder/interactions-panel/show-toast.md).

# Show Toast

The Show Toast interaction displays an overlaid notification that gives the user immediate feedback (info, success, warning, or error) without navigating away.

## Overview

Use a toast message to confirm a user's action and provide feedback. Toasts are overlaid notifications that stack horizontally and can be dismissed by the user.

Use a toast for one of these types of responses:

* **`Info:`** inform users that their actions have triggered a process, and they may have to wait for completion before proceeding.
* **`Success:`** Confirm a successful or completed action.
* **`Warning:`** Warning toasts inform users of potential issues related to their actions and guide them to prevent future problems.
* **`Error:`** Communicate an issue preventing a user from completing their current action and can be fixed within their current flow.

In general, use a toast interaction in response to user action. To decide whether you should use Toasts or another type of messaging, jump to Toasts vs. Alert Modal vs. Confirm interaction.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2Fgit-blob-9eaeda77c43d4ffa1ce6776640186bf23607abbc%2F2022-11-06_21-39-14.png?alt=media" alt=""><figcaption></figcaption></figure>

## Configuration

<table><thead><tr><th width="214">Property</th><th>Description</th></tr></thead><tbody><tr><td>Title</td><td>Text that will be displayed in the header.</td></tr><tr><td>Message</td><td>Main content message for your toast.</td></tr><tr><td>Variant</td><td>Semantic style of the toast. Choose between <code>Info</code>, <code>Success</code>, <code>Warning</code> and <code>Error</code>.</td></tr><tr><td>Mode</td><td>Determines how persistent the toast is. Choose between <code>Dismissible</code>, <code>Pester</code> and <code>Sticky</code>.</td></tr></tbody></table>

### Mode definition

* **Dismissible**: The toast message is dismissed automatically after 5 seconds. Users can close it.
* **Pester**: The toast message is dismissed automatically after 5 seconds. Users can't close it.
* **Sticky**: The toast message is displayed until dismissed, no duration applies. This forces the user to acknowledge info without blocking other interactions on the page.


---

# 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.avonnicomponents.com/flow/component-builder/interactions-panel/show-toast.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.