Purpose
This block transfers files as objects: between File Manager and storage, across storage connections or between folders in one location. Copy keeps the original; move removes it from the source after successful delivery. To transform table contents, use a file source, processing blocks and a file destination.
Inputs and outputs
The input is optional. Without a connection the block runs at the beginning; after another block it follows that dependency. “Success” and “Failure” outputs allow continuation. Actual changes occur during the write stage.
Configuration
- Source: location and folder; selected files/folders, all files in the folder, or all contents including subfolders.
- Destination: location and folder with write access.
- Action: copy or move.
- Name collision: unique adds a number; overwrite creates a new version/replacement according to storage; skip leaves it; error stops.
- Item selection supports up to 500 objects; a folder includes its contents.
Setup
- Test both connections and folder permissions.
- Select source scope, destination and action.
- Choose the collision rule explicitly.
- Inspect prepared operations in simulation.
- Run a controlled test and verify destination files and, for move, source state.
Behavior and checks
Simulation and validation do not transfer files. A folder cannot be moved into itself. Copying into the same folder requires a new unique name. Move removes only delivered objects; trash behavior depends on storage. A Google Drive document is not always a regular downloadable file for this scenario—check its type. After a partial operation, reconcile completed actions before deciding what to repeat.
Example: incoming files and archive
After a successful sales load, connect the destination’s success output to file transfer. Use Incoming as the source, Archive as the destination, move as the action and unique for collisions. Failed loads should not enter the archive branch. Begin with copy in a sample folder to verify configuration.