> 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/accept-popup.md).

# Accept Popup

This is a pre-built Action located under the **@BrowserPopUp Element**. The functionality of this Action in Avo Assure is to accept the popup message that appears in the browser during debugging or execution. 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>(Optional);<Dynamic Variable>(Optional)`

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

### **Example:** Accepting a Browser Popup Alert

In this example, we explain how to handle and accept a browser popup alert using the **Accept Popup** action.

* **Action**: Accept Popup
* **Input Value**: N/A
  * This action does not require any input value. It is used to accept a browser alert or confirmation popup during execution.
* **Output Value**: {Popup}
  * The result of the popup handling is stored in this **{Popup}** dynamic variable with the following possible values:
    * **True**: If the popup is accepted successfully.
    * **False**: If the popup is not accepted successfully.
* **Logical Explanation**: The **Accept Popup** action identifies any browser alert or confirmation popup that appears during execution and accepts it. The result of this operation is stored in the **{Popup}** variable as true.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F8GfanfblaA18dh9Tr9hN%2Fimage.png?alt=media&amp;token=fcde0ce2-a569-44a7-abfc-f0b913316a0b" 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/accept-popup.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.