Skip to main content
Node type: read_file · Version: 1 · Category: Data Read text from an approved file. This node is not marked with the catalogue’s generic side-effect flag. That classification is not a guarantee that every configured operation is read-only; review the concrete action and its destination.

​
When to use this node

  • Load a text, JSON, CSV, or prompt file from an approved path.
  • Pass file content to a parser, AI, or Code node.

​
Example: Read a JSON settings file

Read at most 1 MiB of UTF-8 text, then map content to Parse JSON.
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. Select or map a trusted file path.
  2. Keep maximumBytes close to the expected file size.
  3. Map content into Parse JSON and inspect its value output.

​
Configuration

Only UTF-8 text is accepted. The byte limit is clamped to 1–104857600 bytes.

​
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 node returns content, the trusted path, and bytes read.
  • The maximum size is enforced before unbounded file content enters execution data.
  • The editor catalogue declares content (string), 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

  • Binary files are not appropriate input; use a node designed for that artifact.
  • A plain string path from an untrusted source may not carry the approval provenance required by the runner.

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