> 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/generic/file-and-folder-operations/verify-file-exists.md).

# Verify File Exists

The Verify File Exists action in the Avo Assure is found under the **@Generic Element** is used to verify if the file is present in the given location or not and store the result in an dynamic variable.

### **Syntax**

**Input Value:** `<file_path>;<File_name.extn>`

| Argument                                | Description                                                                                                                                                                                        |
| --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p>\<file\_path></p><p>(Required)</p>   | Specify the file location where the file is expected to be found.                                                                                                                                  |
| <p>\<File\_name.extn><br>(Required)</p> | <p>Complete name of the file including its extension<br><strong>Note:</strong> <em>All types of file formats are supported (e.g.,</em> .<em>txt. .xlsx, .xls, .pdf, .gif, .doc, .xml,etc)</em></p> |

**Output value:**

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

**Example:**

**Verify the existence of a specified file**\
\
The **Verify File Exists** action checks whether a file with the specified name and extension exists at the provided file path (e.g., **C:\sam;Report.txt**). The result of the check is stored in the **{Status}** variable with the following possible values:

* **True** – if the file exists at the given location
* **False** – if the file does not exist or the path is invalid

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F9JVc74biM1a0d6tTqY28%2Fimage.png?alt=media&amp;token=8001ea65-c1d7-4790-84c4-8b9b930603be" 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/generic/file-and-folder-operations/verify-file-exists.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.