> 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-1/verifytextexist.md).

# verifyTextExist

This is a pre-built Action located under the captured table element. The functionality of this Action in Avo Assure is to verify the presence of the specified text in the table and count its occurrences based on the input provided. The result is stored in the given dynamic variable for further use during test execution.

## **Syntax**

**Input Value**: `<text>`

| Argument                     | Description                                                                           |
| ---------------------------- | ------------------------------------------------------------------------------------- |
| <p>\<text><br>(Required)</p> | Provide the text value you want to verify for its existence within the table content. |

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

| 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 stores the status as **True** or **False**.      |

### **Example: Verifying and Counting Text Occurrences in a Table**

In this example, we explain how to verify whether a specific text exists within a captured table and count how many times it appears.

* **Action**: VerifyTextExist
* **Input Value**: Home Improvement Loan
  * This action requires the exact text (**Home Improvement Loan**) that needs to be searched within the table.
* **Output Value**: {Count}
  * The total number of occurrences of the specified text found in the table (6) is stored in the **{Count}** dynamic variable.
  * If a second output variable is provided, the action returns the status as **True** or **False**:
    * **True**: If the text is found in the table and its occurrences are counted successfully.
    * **False**: If the text is not found in the table.
* **Logical Explanation**: The **verifyTextExist** action reads the expected text from the **Input Value** column (**Home Improvement Loan**). It scans through the captured table, identifies all cells containing the specified text, counts the total number of occurrences. The result is stores (6) in the **{Count}** variable.

<figure><img src="/files/YRUw06U5bCnIstTPW9eH" 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/web/table-1/verifytextexist.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.