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

# Rename Folder

The Rename Folder action in the Avo Assure is found under the **@Generic Element** is used to rename the existing folder name to the new folder name and store the result in an dynamic variable.

### **Syntax**

**Input Value:** `<folder_path>;<folder_name_old>;<folder_name_new>`

| Argument                                  | Description                                                    |
| ----------------------------------------- | -------------------------------------------------------------- |
| <p>\<folder\_path></p><p>(Required)</p>   | Specify the folder location where the folder currently exists. |
| <p>\<folder\_name\_old><br>(Required)</p> | Current name of the folder you want to rename.                 |
| <p>\<folder\_name><br>(Required)</p>      | The new name you want to assign to the folder.                 |

**Output value:**

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

**Example**

**Rename an existing folder to a new name at the specified path**\
\
The **Rename Folder** action renames an existing folder located at the given path (e.g.,**C:\sam;ProjectFiles;Updated file**). This helps organize files by updating folder names dynamically. The action status is saved in the **{Status}** variable with the following possible values:

* **True** – if the folder is renamed successfully
* **False** –if the folder does not exist, the new name is invalid, or the renaming fails

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F37rB5M2jt0j5iXnvSeCG%2Fimage.png?alt=media&amp;token=072157a5-a96f-4867-b1a2-4b6458d0c052" 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/rename-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.