Skip to main content
Node type: delete_path · Version: 1 · Category: System Delete an explicitly approved path. sndbox classifies this node as side-effecting, so tests or automatic runs can require additional confirmation and permission review.

​
When to use this node

  • Remove a temporary artifact after the workflow has verified its durable destination.
  • Clean an approved staging folder with explicit review.

​
Example: Remove a processed temporary file

Delete one mapped file after a successful upload, without allowing recursive folder deletion.
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. Map a trusted path from the node that created the file.
  2. Keep recursive disabled for a single-file cleanup.
  3. Place deletion after every step that still needs the artifact.

​
Configuration

The selected path must be inside an approved folder. Test runs require an additional destructive-action confirmation.

​
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

  • The path must remain inside an approved filesystem boundary.
  • recursive authorizes non-empty directory removal and materially expands the operation.
  • 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

  • Test runs ask for destructive-action confirmation.
  • Deletion is not an archive; move the artifact instead if recovery might be needed.

​
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.