> 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/element/verify-element-exists.md).

# Verify element exists

This is a pre-built action available under the **Captured Element** from the **Desktop Application**. The functionality of this action in Avo Assure is to verify the presence of the element in the application, and save the result in dynamic variable.

### Syntax

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

| Argument                             | Description                                                        |
| ------------------------------------ | ------------------------------------------------------------------ |
| <p>\<element text><br>(Required)</p> | Provide the text to be verified against the captured element text. |

**Output Value:**

| Argument                                                    | Description                                                                    |
| ----------------------------------------------------------- | ------------------------------------------------------------------------------ |
| \<Dynamic Variable>(Optional);\<Dynamic Variable>(Optional) | This dynamic variable holds the status of the action as **True** or **False.** |

**Example**

**Checks for the presence of a specified element on the screen**

The **Verify element exists** action takes no input value and verifies whether the specified element is present and visible on the screen. The result of the verification operation is stored in the **{Element Exists}** variable as **Ture** (if the element verified successfully) or **False** (if the element not verified successfully).

<figure><img src="/files/BoYnE1qO0ooY7KJq4jGD" 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 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.avoautomation.com/avo-assure/actions/desktop/element/verify-element-exists.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.