> 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/click-on-element.md).

# Click on Element

This pre-built Action located under the **@Custom Element.** The functionality of this action in Avo Assure to perform a click operation on the element specified in the Input Value and stores the result in a dynamic variable.

### Syntax

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

| Argument                            | Description                                                                                                               |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| <p>\<ObjectType><br>(Required)</p>  | Specific type of object to be clicked. (e.g., button, link )                                                              |
| <p>\<VisibleText><br>(Optional)</p> | The visible text associated with 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="info" %}
**Note:**

* If for last argument abs is defined then the Action must be executed with absolute preformation with the specified **absolute X path** in the input.
* To skip an optional input value, use an extra semicolon (**;**).
  {% endhint %}

**Output Value**

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

### **Example 1: Clicking an Element by Its Visible Text**

In this example, we explain how to click an element using its visible text when the element is not captured in the Element Repository.

* **Action**: Click on Element
* **Input Value**: link;Forgot Password;0
  * The first part (**link**) specifies the type of element to identify.
  * The second part (**Forgot Password**) specifies the visible text of the element.
  * The third part (**0**) specifies the index of the matching element to click.
* **Output Value**: N/A
* **Logical Explanation**: The **Click on Element** action takes the value from the Input Value column (**link;Forgot Password;0**). This action identifies the link with the visible text **Forgot Password** and clicks the first matching element based on the specified index.

{% hint style="info" %}
**Note**: The index starts from 0, where 0 represents the first matching element.
{% endhint %}

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FMRTSJiIvtTxD2OXpjZSL%2Fimage.png?alt=media&amp;token=6cfbe6c4-a1a8-40f5-bfb1-59ce25aaf994" alt=""><figcaption></figcaption></figure>

#### **Example 2: Clicking an Element Using an Optional Parameter**

In this example, we explain how to click an element using its visible text and absolute XPath when the element is not captured in the Element Repository.

* **Action**: Click on Element
* **Input Value**: button;Log In;0;/html/body/div/div/div/div/div/div\[1]/button
  * The first part (**button**) specifies the type of element to identify.
  * The second part (**Log In**) specifies the visible text of the element.
  * The third part (**0**) specifies the index of the matching element to click.
  * The fourth part (**/html/body/div/div/div/div/div/div\[1]/button**) specifies the absolute XPath of the element.
* **Output Value**: N/A
* **Logical Explanation**: The **Click on Element** Action takes the value from the **Input Value** column (**button;Log In;0;/html/body/div/div/div/div/div/div\[1]/button**). It identifies the button using the specified object type, visible text, index, and absolute XPath, and performs the click operation on the matching element.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FynBYYtxjBc6oGFMRmxms%2Fimage.png?alt=media&amp;token=5f233f72-79d7-429c-8b58-85448b27f785" 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/custom/click-on-element.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.
