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

# Click on Table Cell

This is pre-built Action located under the Table captured from the AUT Element Name, instructs Avo Assure to perform a click operation on the grid cell given in the input and save the result in dynamic variable.

### Syntax

**Input Value:** `<Row>;<Column>;<header/body>(optional);<left/right>(optional);<row_attr>(optional);<col_attr>(optional)`

<table><thead><tr><th>Argument</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td>&#x3C;Row><br>(Required)</td><td>Specifies the target row number</td><td></td></tr><tr><td>&#x3C;Column><br>(Required)</td><td>Specifies the target column by number or column name.</td><td></td></tr><tr><td><p>&#x3C;header/body></p><p>(Optional)</p></td><td>Defines whether the verification should be performed in the header or body of the table.</td><td></td></tr><tr><td><p>&#x3C;left/right></p><p>(Optional)</p></td><td>Defines the direction to search within the row.</td><td></td></tr><tr><td>&#x3C;row_attr><br>(Optional)</td><td>Additional row-based attribute or identifier for more specific targeting</td><td></td></tr><tr><td>&#x3C;col_attr><br>(Optional)</td><td>Additional column-based attribute or identifier for column selection</td><td></td></tr></tbody></table>

**Output Value:**

| Argument                                                    | Description                                              |
| ----------------------------------------------------------- | -------------------------------------------------------- |
| \<Dynamic Variable>(Optional);\<Dynamic Variable>(Optional) | This variable stores the status as **true** or **false** |

**Example**

**Clicks a specific cell in a table based on row and column information**\
\
The **Click on Table Cell** action interacts with a targeted cell in a table using the input value format (e.g., **2;3;body**). In this case, **2** is the row number, **3** is the column number, and **body** specifies the section of the table. The click result is stored in the **{ClickCell}** 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%2FUUq7E8MQTFqVKgH1A3yi%2Fimage.png?alt=media&amp;token=47d8716f-2844-4379-9259-e0f45b4a20cf" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FtEHHkO2tDaZG4vCKQCHZ%2Fimage.png?alt=media&amp;token=8c9f1ae4-6b18-44a2-90c1-95c7e8696277" 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/grid/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.
