> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/automations/actions/transfer-actions.md).

# Transfer Actions

Learn about the Transfer Action category in Automations.

Transfer actions are one of the primary use cases for workflows in Couchdrop. This category of actions contains actions for moving, transferring, and deleting files. 

These transfer actions can also involve external parties, such as sending a file to a remote SFTP server. 

### Available Transfer Actions

<table><thead><tr><th width="216">Action</th><th>Description</th></tr></thead><tbody><tr><td>Rename File</td><td>Rename a file. The file name can contain any <a href="/automations/variables.md">automation variable</a>.</td></tr><tr><td>Move File</td><td>Move the original file to a new destination. </td></tr><tr><td>Transfer/Copy</td><td>Make a copy of the file at another location. You choose whether to always overwrite files with the same name or only overwrite files with the same name if the modificaiton time is newer. </td></tr><tr><td>Delete File</td><td>Delete the file the workflow is acting on. </td></tr></tbody></table>


---

# 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.couchdrop.io/automations/actions/transfer-actions.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.