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

# Delete Folder

The Delete Folder action located under **@Generic Element** is used to delete the folder located at the path specified in the input and store the result in an dynamic variable.

### **Syntax**

**Input value:** `<folder path>;<folder name>;<index>`

| Argument                               | Description                                                                                                                                                                          |
| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| <p>\<folder path></p><p>(Required)</p> | Specify the folder location where the folder to be deleted is located.                                                                                                               |
| <p>\<folder name><br>(Required)</p>    | Provide name of the folder to be deleted.                                                                                                                                            |
| <p>\<index><br>(Required)</p>          | <p>Index value to identify which folder to delete in case multiple folders with the same base name exist.<br><strong>Note:</strong> Index value start from “<strong>0</strong>”.</p> |

**Output value:**

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

**Example**

**Delete a folder by name and index at the specified path**\
\
The **Delete Folder** action removes a folder with the specified name and index from the given path (e.g., **C:\sam;Updated file;0**). The action status is saved in the **{Status}** variable with the following possible values:

* **True** – if the folder is deleted successfully
* **False** –if the folder does not exist or deletion fails

{% hint style="warning" %}
**Note:** The index is used to identify the correct folder if multiple folders with the same name exist.
{% endhint %}

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FjcJdYtRoSWiuJ2373Bke%2Fimage.png?alt=media&amp;token=818596b0-bca0-40f7-8631-cd8a695b519f" 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/delete-folder.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.