Skip to main content
sndbox distinguishes ordinary JSON-compatible values from local path and connection references. File nodes establish or preserve a trusted path boundary; data nodes shape, parse, compare, or store values.

​
Choose the right node

Files and folders

Read, write, move, copy, delete, and list approved paths.

Parsers

Turn CSV, JSON, or text files and mapped content into structured output.

HTTP

Call an endpoint with explicit method, headers, query, body, timeout, and retry.

Workflow state

Read prior successful state and detect meaningful changes across runs.

​
Mapped content wins

CSV, JSON, and text parsers accept either an optional approved file or mapped/pasted content. When both exist, mapped content takes precedence. This makes a parser reusable after HTTP, browser extraction, download, or file-read nodes without guessing which source was used.

​
Inspect actual types

Test the producer and inspect its output before selecting a nested path. Node reference pages list each typed input and output port generated from the source catalogue.