> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sndbox.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Files and data

> Move trusted paths and JSON-compatible values through explicit parser, state, and network nodes.

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

<CardGroup cols={2}>
  <Card title="Files and folders" icon="folder" href="/files-and-data/files-and-folders">Read, write, move, copy, delete, and list approved paths.</Card>
  <Card title="Parsers" icon="braces" href="/files-and-data/csv">Turn CSV, JSON, or text files and mapped content into structured output.</Card>
  <Card title="HTTP" icon="globe" href="/files-and-data/http-requests">Call an endpoint with explicit method, headers, query, body, timeout, and retry.</Card>
  <Card title="Workflow state" icon="history" href="/files-and-data/workflow-state">Read prior successful state and detect meaningful changes across runs.</Card>
</CardGroup>

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