> For the complete documentation index, see [llms.txt](https://docs.gpmautomate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gpmautomate.com/automate-en/action-guide/file-and-folder/move-rename-folder.md).
# Move / rename folder
Move / rename folder is a versatile action used to move an entire folder (including all files and subfolders inside) to a new location, or to rename that folder right at its current location on the hard drive.
Similar to operations with files, this action will completely cut the folder to the new location (if moving) or entirely replace the old name (if renaming).
🎥 Watch the tutorial video: [Here](https://youtu.be/EH7olDLAb9c).
#### Configuration parameters:
* Source Folder: The absolute path of the source folder that needs to be moved or renamed (e.g., `D:\GPM_Data\old_name`).
* Destination Folder: The absolute path of the destination folder to move to, or the path containing the new folder name after renaming (e.g., `E:\Backup_Data\old_name` or `D:\GPM_Data\new_name`).
#### Practical example 1: Rename folder
You have a folder containing temporary data named `temp_data`. After the script has processed all the data inside, you want to rename this folder to `processed_data` to mark it as completed.
* Source Folder: `D:\GPM_Data\temp_data`
* Destination Folder: `D:\GPM_Data\processed_data` *(keep the parent path unchanged, only change the folder name at the end)*.
* Result: The folder `temp_data` will be immediately renamed to `processed_data`.
---
# 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.gpmautomate.com/automate-en/action-guide/file-and-folder/move-rename-folder.md?ask=&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.
