Skip to main content
Node type: copy_path · Version: 1 · Category: System Copy within approved folders. sndbox classifies this node as side-effecting, so tests or automatic runs can require additional confirmation and permission review.

​
When to use this node

  • Create a backup before a destructive or mutating step.
  • Copy a file or folder between approved local boundaries.

​
Example: Back up a configuration folder

Copy a reviewed source folder into a dated backup destination.
Example settings
This shows the important settings, not a complete exported node. Local paths must be selected, mapped from a trusted path, or covered by the runner’s approved boundary.
  1. Approve the source and destination boundaries.
  2. Leave overwrite disabled for the first run.
  3. Inspect the destination and copied entry count before relying on the backup.

​
Configuration

​
Workflow JSON

The editor stores this node with the following implemented default configuration:
Default node configuration
Values may be entered literally or mapped from an earlier compatible output when the inspector exposes a mapping control. See Variables and data mapping.

​
Inputs

This node has no typed ports in this direction.

​
Outputs

​
Execution behavior

  • Files and folders are supported, and the output identifies source, destination, and copied entry count.
  • Replacement is rejected unless overwrite is explicitly enabled.
  • The editor catalogue declares result (any) for mapping. The execution inspector can contain additional evidence fields; inspect a real result before selecting nested paths from object or any outputs.

​
Common issues

  • Copying a folder into itself or a descendant is invalid.
  • Large directory trees can take time and produce many filesystem operations.

​
Where it can run

  • Desktop local runner
  • Paired self-hosted runner
  • Hosted runner

​
Test and inspect

Use Test node in the editor to preview this step with the current configuration. A full run records resolved inputs, outputs, logs, duration, and any artifacts in the execution inspector. Side-effecting or destructive nodes can require an additional confirmation or approved workflow permission.