> 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-file.md).

# Rename File

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

### **Syntax**

**Input Value:** `<file_path>;<file_name.extn>;<file_name2.extn>`

| Argument                                 | Description                                                                                                                                                              |
| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| <p>\<file\_path></p><p>(Required)</p>    | Specify the folder location where the file currently exists                                                                                                              |
| <p>\<file\_name.extn><br>(Required)</p>  | Current name of the file (with extension) that you want to rename.                                                                                                       |
| <p>\<file\_name2.extn><br>(Required)</p> | <p>The new name (with extension) that you want to assign to the file.<br><strong>Note:</strong> Supported file formats are .txt. .xlsx, .xls, .pdf, .gif, .doc, .xml</p> |

**Output Value:**

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

**Example**

**Rename a specified file to a new name**\
\
The **Rename File** action renames an existing file from its current name to a new name at the given file path (e.g., **C:\sam;Report.txt;Updated Report.txt**). The status of the renaming operation is stored in the **{Status}** variable with the following possible values:

* **True** – if the file is renamed successfully
* **False** – if the file does not exist or the renaming operation fails (e.g., file with same name already exists.)

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FoZbv5qSn9ZWtVaAOWcZX%2Fimage.png?alt=media&amp;token=06c6ab91-578d-49c6-a62f-34e86bf539a2" 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-file.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.