> 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-folder-exists.md).

# Verify Folder Exists

The Verify Folder Exists action in the Avo Assure is found under the **@Generic Element** is used to check if a folder exists at the specified location and store the result in an dynamic variable.

### **Syntax**

**Input Value: `<folder_path>;<folder_name>`**

| Argument                                | Description                                                       |
| --------------------------------------- | ----------------------------------------------------------------- |
| <p>\<folder\_path></p><p>(Required)</p> | Specify the folder location where the folder is expected to exist |
| <p>\<folder\_name><br>(Required)</p>    | Provide name of the folder to verify under the given path.        |

**Output Value:**

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

**Example**

**Verify whether a specified folder exists at a given path**\
\
The **Verify Folder Exists** action checks whether a folder with the specified name exists at the provided location (e.g., **C:\sam;ProjectFiles**). The verification result is stored in the **{Status}** variable with the following possible values:

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

<figure><img src="/files/crXyGcljdapCUZtP2Qd2" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.avoautomation.com/avo-assure/actions/generic/file-and-folder-operations/verify-folder-exists.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.