> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/web/browser-popup/get-popup-text.md).

# Get Popup Text

This is a pre-built Action located under the **@BrowserPopUp Element**. The functionality of this Action in Avo Assure is to fetch the text from a browser popup. The result is stored in a dynamic variable for further use during test execution.

## Syntax

**Input Value**: `N/A`

<table><thead><tr><th>Argument</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td>N/A</td><td>Not Applicable</td><td></td></tr></tbody></table>

**Output Value**: `<Dynamic Variable>;<Dynamic Variable>(Optional)`

<table><thead><tr><th>Argument</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td><p>&#x3C;Dynamic Variable></p><p>(Required)</p></td><td>This dynamic variable stores the popup text.</td><td></td></tr><tr><td><p>&#x3C;Dynamic Variable></p><p>(Optional)</p></td><td>This dynamic variable stores the status as <strong>True</strong> or <strong>False</strong>.</td><td></td></tr></tbody></table>

### Example: Retrieving Message from a Browser Popup

In this example, we explain how to retrieve the text message displayed in a browser popup using the **Get Popup Text** action.

* **Action**: Get Popup Text
* **Input Value**: N/A
  * This action does not require any input value in the **Input Value** column. It retrieves the message displayed in the active browser popup.
* **Output Value**: {Popup Text}
  * The retrieved popup message (e.g., This is a Simple Alert) is stored in this **{Popup Text}** dynamic variable.
  * If a second output variable is provided, the action returns the status as True/False:
    * **True**: If the popup text is fetched successfully.
    * **False**: If the popup text is not fetched successfully.
* **Logical Explanation**: The **Get Popup Text** action reads and retrieves the message from the currently displayed browser alert or confirmation popup. The fetched text is stored in the **{Popup Text}** variable (e.g., This is a Simple Alert).

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FuDR5eo6qfdiKfsAh2jmG%2Fimage.png?alt=media&amp;token=04e5b27a-fcbe-4559-bf41-f967a44bf29a" alt=""><figcaption></figcaption></figure>


---

# 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.avoautomation.com/avo-assure/actions/web/browser-popup/get-popup-text.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.