> 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/table/verify-text-exist.md).

# Verify Text Exist

This pre-built action, located under the table captured from the AUT element, instructs Avo Assure to verify the presence of the specified text and count its occurrences in the table, based on the input provided. The result is stored in the specified dynamic variable.

### **Syntax**

**Input Value:** `<Text>`

| Argument                     | Description                                                      |
| ---------------------------- | ---------------------------------------------------------------- |
| <p>\<Text><br>(Required)</p> | Text value to be verified for existence within the table content |

**Output Value**

| Argument                                 | Description                                                                   |
| ---------------------------------------- | ----------------------------------------------------------------------------- |
| <p>\<Dynamic Variable><br>(Required)</p> | This dynamic variable stores the count of the specified items present         |
| <p>\<Dynamic Variable><br>(Optional)</p> | This dynamic variable holds the status of the action as **True** or **False** |

**Example**\
\
**Verify and Count Text Occurrences in a Table**

The **Verify Text Exist** action takes the input from the Input Value column (e.g., **Home Improvement Loan**), verifies whether the specified text is present within the table, and counts its occurrences. The count is stored in the **{Count}** variable, and the action status is stored in the **{Status}** variable with the following possible values:

* **True** – if the text is found and count its occurrences in the table
* **False** – if the text is not found

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FjT8iDH4WprKSgEKhQMek%2Fimage.png?alt=media&amp;token=3883e92f-2f5c-40e7-b602-ca05998a7090" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2Fwt6zwCQutsl3pCaPLvUP%2Fimage.png?alt=media&amp;token=9d32e989-14cb-4015-9cc8-16ca0dd52d76" 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/table/verify-text-exist.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.