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

​
When to use this node

  • Save generated text, JSON, CSV, or code to an approved location.
  • Materialize mapped output for another local tool.

​
Example: Write a generated summary

Write mapped text to a new file and create missing parent folders.
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. Choose an approved destination path.
  2. Map text content from the producing node.
  3. Test with overwrite disabled and inspect the returned path and byte count.

​
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

​
Outputs

​
Execution behavior

  • The output contains the written trusted path and byte count.
  • createParents affects only missing parent directories; overwrite separately controls replacement of the target file.
  • The editor catalogue declares path (path), bytes (number) 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

  • The node fails if the file exists and overwrite is false.
  • Validate generated content before writing it to a path consumed by another process.

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