> 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/dropdown/get-selected-value-from-dropdown.md).

# Get Selected Value from Dropdown

This is a pre-built Action located under the captured dropdown element. The functionality of this action in Avo Assure is to retrieve the selected value from the dropdown. The result is stored in the given dynamic variable for further use during test execution.

## **Syntax**

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

| Argument | Description    |
| -------- | -------------- |
| N/A      | Not Applicable |

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

| Argument                                    | Description                                                        |
| ------------------------------------------- | ------------------------------------------------------------------ |
| <p>\<Dynamic Variable></p><p>(Required)</p> | This dynamic variable stores the value selected from the dropdown. |
| <p>\<Dynamic Variable></p><p>(Optional)</p> | This dynamic variable stores the status as **True** or **False**.  |

### **Example: Retrieving the Selected Value from a Dropdown List**

In this example, we explain how to fetch the currently selected option from a dropdown list.

* **Action:** Get Selected Value from Dropdown
* **Input Value:** N/A
  * This action does not require any value in the Input Value column.
* **Output Value:** {Dropdown}
  * The selected dropdown value is (e.g., All) stored in the **{Dropdown}** dynamic variable.
  * If a second output variable is defined, it stores the action status with the following possible values:
    * **True**: If the selected value is retrieved successfully.
    * **False**: If the selected value is not retrieved successfully.
* **Logical Explanation**: The **Get Selected Value from Dropdown** action executes without requiring input. The action fetches the value currently selected in the targeted dropdown element. The retrieved value (e.g., All) is stored in the **{Dropdown}** variable.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FCyAjFgaG6UUkQZ1Q9Vdx%2Fimage.png?alt=media&amp;token=90c3fc4d-7c3e-4626-942e-aaa490da04c0" 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/dropdown/get-selected-value-from-dropdown.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.