> 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/grid/verify-column-header.md).

# Verify Column Header

This is a pre-built action in Avo Assure. This action verifies whether a specific column is **Present** or **Not** **Present** in the grid, and save the result in the dynamic variable.

### Syntax

**Input Value:** `<Column Header Value>`

<table><thead><tr><th>Argument</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td><p>Column Header Value</p><p>(Required)</p></td><td>Required column name of the grid</td><td></td></tr><tr><td><p><em>Not</em></p><p><em>(Optional)</em></p></td><td><em>Not is used when working with negative scenario and it is not case sensitive</em></td><td></td></tr></tbody></table>

**Output Value:**

<table><thead><tr><th>Argument</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td>&#x3C;Dynamic Variable>(Optional);&#x3C;Dynamic Variable>(Optional)</td><td>This variable holds the results in <strong>True</strong> and <strong>False</strong></td><td></td></tr></tbody></table>

### **Example 1**

**Checks if a column header exists or not in the Grid**\
\
The **Verify Column Header** action takes the value from the Input Value column (e.g., **Date;Not**) and checks whether the specified column header **(Date)** exists in the Grid. If "**Not**" is provided, it checks for the absence of the column. The result is stored in the **{Header}** variable, while the execution status is stored in the **{Status}** variable, with the following possible values:

* **True** – if the header is found
* **False** – if the header is not found

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FZACwwvEU3qm0fs8pbQk8%2Fimage.png?alt=media&amp;token=163226ce-ae1c-46b6-bade-592e0c7bb8e6" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FIjqb47iZodYVPoR3KhEO%2Fimage.png?alt=media&amp;token=a7ad796d-73c5-42e9-948a-f70ced63bcb3" alt=""><figcaption></figcaption></figure>

### **Example 2**

**Verify Column Header (Year)**\
\
The **Verify Column Header** action takes the value from the Input Value column (**Year**) and verifies whether the specified column header exists in the Grid. The result of the verification is stored in the **{Header}** variable, while the execution status is stored in the **{Status}** variable, with the following possible values:

* **True** – if the column header is found.
* **False** – if the column header is not found or an error occurs.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2Fw3wxOIFHQIf32ND4i6J0%2Fimage.png?alt=media&amp;token=0edfd555-95e0-4b43-9742-ceff415c6c31" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FjPNrHulPkbzw3j1g5JMi%2Fimage.png?alt=media&amp;token=3ffb0eed-4cd2-4a06-af6c-cd74e0604e96" 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/grid/verify-column-header.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.