> 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/custom/get-object-count-on-web-page.md).

# Get Object Count on Web Page

This is a pre-built Action located under the **Custom Element.** The functionality of this action in Avo Assure to find the number of occurrences of the object on the web page, and the result is stored in a dynamic variable.

### **Syntax**

**Input Value:**`<ObjectType>;<VisibleText(optional)>;<Index>;<abs(optional)>`

| Argument                            | Description                                                                                                               |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| <p>\<ObjectType><br>(Required)</p>  | Specify the type of the object                                                                                            |
| <p>\<VisibleText><br>(Optional)</p> | Enter the visible text on the object                                                                                      |
| <p>\<Index><br>(Required)</p>       | Provide the position of the element, which helps to identify the value based on the sequence in list . (starting from 0)​ |
| <p>\<abs><br>(Optional)</p>         | If the **abs** is provided, the action is performed with absolute identification using the **absolute X path**            |

{% hint style="warning" %}
**Note:** The user needs to provide the type of object, its visible text of the element (if needed), its index, and the abs.

*To skip an optional input value, use an extra semicolon (;).*
{% endhint %}

**Output Value**

| Argument                                    | Description                                                     |
| ------------------------------------------- | --------------------------------------------------------------- |
| <p>\<Dynamic Variable><br>(Required)</p>    | This dynamic variable holds the total number of objects found   |
| <p>\<Dynamic Variable></p><p>(Optional)</p> | This dynamic variable holds the status as **True** or **False** |

**Example**

**Retrieves the count of matching objects present on the web page**

The **Get Object Count on Web Page** action takes the value from the Input Value column (e.g., **textbox;;0**) and identifies all matching elements based on the provided object type and other optional parameters. The result of the count is stored in the **{Count}** variable, while the execution status is stored in the **{Status}** variable, with the following possible values:

* **True** – if the object count is retrieved successfully.
* **False** – if the count retrieval fails

<figure><img src="/files/TReCKd69SEsNfLf5wFBB" 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/custom/get-object-count-on-web-page.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.