File Copy — Reference
Copy a server file into another folder and return the actual destination path.
Copy a server file into another folder and return the actual destination path.
Before you begin
Section titled “Before you begin”- A Server Connect action and a dedicated test file/folder that the server process can access. Protect the endpoint before exposing private file operations.
File Copy
Section titled “File Copy”Copy a server file into another folder and return the actual destination path.
Choose a server path
Section titled “Choose a server path”Use an application-relative path beginning with /. In a standard Node.js project, /public/uploads/example.txt is a server path while /uploads/example.txt is its public URL. PHP paths are relative to the application root determined by its runtime. Verify the active target with the file picker instead of copying a path between server models. Do not accept unrestricted user input as a filesystem path.
Settings
Section titled “Settings”| Setting | Meaning |
|---|---|
| Name | Names the operation’s result for later server steps when it returns one. See the result notes for this operation; not all file actions return the same type. |
| File Path | The application-relative path of the server file. This is not the browser’s local file-picker path or an HTTP URL. |
| To Folder | The destination directory. The runtime appends the source filename; choose File Rename separately when the filename must change. |
| Overwrite | Allows replacing an existing destination. Default off. Copy/Move can choose a unique name when off; Rename with a fixed existing target can fail instead. |
| Create Folder | Creates missing destination directories when enabled. Runtime default on. When disabled, the destination folder must already exist. |
| Output Result | Includes a named returned result in action output when applicable. Default off. Check the operation’s actual return type; Download sends the file response instead. |
Worked example
Section titled “Worked example”Copy a disposable example.txt to a dedicated archive folder with Overwrite off. Verify that the original remains and the destination has identical content. Copy it again and inspect the returned path rather than assuming the name stayed example.txt.
Result and runtime limits
Section titled “Result and runtime limits”To Folder is a directory, not the full destination filename. The runtime appends the source basename. With Overwrite off, a name collision can produce a unique suffixed filename instead of an error. Use the returned path in later steps.
Connect files to the application
Section titled “Connect files to the application”A returned path or URL is not an access-control decision. Keep private file reads and writes behind server-side identity and ownership checks, and update any database metadata only after the intended file operation succeeds.
Check your result
Section titled “Check your result”You can configure the path and verify the returned result or file effect without confusing it with a page URL or database update.