> For the complete documentation index, see [llms.txt](https://docs.heisenware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heisenware.com/reference/widgets/display/toast.md).

# Toast

The toast is an App action now: drop it on an output or an error handler, or on a button

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-7a606254d64ed369041eb10ad256afd5b69eeda2%2Fwidget-toast.png?alt=media" alt="Three toasts stacked in the corner: an error that the label printer is not reachable, a warning about low cherry syrup, and a success message that an order was saved" width="394"><figcaption></figcaption></figure>

A toast pops up a short message and fades away again: a success, a warning, an error or an info. It is no longer a widget you place on a page. It is an [App action](https://docs.heisenware.com/app-builder/app-builder/pages.md#app-actions), like Logout or Open link: drag the **Toast** chip from the foot of the Pages and actions explorer.

* **On an output or an error handler**: every value the output produces pops one toast, whatever page the user is on. Switch on *Take message from the live value* and the value becomes the message: an error handler's error reads "message, because: cause". With the switch off, the toast shows the message you typed, and the value only decides that it pops.
* **On a button, icon or image**: a click pops the toast with the message you typed.

Type, display time and position are set in the same dialog. Click the toast's chip on the Flowboard to change them later.

{% hint style="info" %}
Apps built with a toast widget keep working: the App Builder turns every toast widget into a Toast action on the output or error handler it was linked to, and removes the widget. A toast that was copied to several pages becomes one action and pops once.
{% 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.heisenware.com/reference/widgets/display/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.
