> 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/desktop/button/get-button-name.md).
# Get button name
This is a pre-built action available under the **Captured Button Element** from the **Desktop Application.** The functionality of this action in Avo Assure is to retrieve the button name which is captured and save the result in dynamic variable
### **Syntax**
**Input Value:** `N/A`
| Argument | Description |
| -------- | -------------- |
| N/A | Not Applicable |
**Output Value:**
| Argument | Description |
| ---------------------------------------- | ------------------------------------------------------------------------------ |
|
\ (Required)
| This dynamic variable holds the retrieve button name |
|
\ (Optional)
| This dynamic variabel holds the result of this action as **Ture** or **False** |
**Example**
**Retrieves the name of the specified button from the application.**
The **Get button name** action does not take any value in the Input Value column. It fetches the name of the target button. The result of the operation is stored in the **{Button Name}** variable (e.g., **Log In**)
---
# 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/desktop/button/get-button-name.md?ask=&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.
