> For the complete documentation index, see [llms.txt](https://docs.trysavvy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trysavvy.com/other-useful-docs/work-in-progress/pending/work-in-progress-how-to-add-an-info-box-popup.md).

# Work in Progress: How to Add an Info Box Popup

{% hint style="info" %}
An Info Box Popup is a graphical user interface ( GUI ) display area that slides from the bottom of the flow. In flows, we usually use them to display a message that expands some piece of information.
{% endhint %}

### Step 1: Create the Popup page

* Create a new page
* Name it with a key that shows that the page is a popup "popup\_myname"
* Add content to the page
* Hide the page

### Step 2: Create the trigger for the popup

* Create a new Rich Text component
* Select the link option
* Link it to `open_popup:popup_myname`
* Enjoy! 


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.trysavvy.com/other-useful-docs/work-in-progress/pending/work-in-progress-how-to-add-an-info-box-popup.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.