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

# Click on Table Cell

This is a pre-built Action located under the Table captured from the AUT Element, instructs the Avo Assure to click on specific cell within a dynamic web table during debugging or execution, and the result is stored in a dynamic variable.

### Syntax

**Input Value:** `<Row>;<Column>;<ObjectType>;<Index>`

| Argument                           | Description                                                                                                                                                              |
| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| <p>\<Row><br>(Required)</p>        | Specify row number of the table cell to be clicked                                                                                                                       |
| <p>\<Column><br>(Required)</p>     | Specify column number of the table cell                                                                                                                                  |
| <p>\<ObjectType><br>(Required)</p> | <p>Type of object inside the cell<br>Object Type values must be one of the following:<br>(e.g., textbox, button, link, img, checkbox, radiobutton, div, span ect., )</p> |
| <p>\<Index><br>(Required)</p>      | Index of the object inside the cell (starting from 0)                                                                                                                    |

#### Output Value

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

**Example**

**Performs a click action on a specific cell within a table based**

The **Click on Table Cell** action takes the value from the Input Value column (e.g., **2;3;textbox;1**) and performs a click on the specified cell in the table, based on the given row and column position, object type, and its index on the screen. The result of the click operation is stored in the **{CellClick}** variable, , with the following possible values:

* **True** – if the cell is clicked successfully.
* **False** – if the click fails or an error occurs

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FyecA2uU3DjRz8y0etljp%2Fimage.png?alt=media&amp;token=bbeb023d-d698-4384-a7d3-497e0b89cfa3" 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/click-on-table-cell.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.
