All nodes/Integrations/Files

Local FS Config (DEV ONLY)

DEV ONLY. A local server folder as the file store for File Glob/Read/Write/Tool — the WebDAV Config counterpart on local disk. Disabled in production and restricted to LOCAL_FS_ALLOWED_ROOTS.

Try it

When to use it

The node makes a directory on the backend server’s disk the root of a file store. It exists for development and debugging — running a workflow over a folder of test files without setting up an external disk, for example.

In production these nodes are disabled outright. A permanent external disk is WebDAV Config, and the platform’s own files are WS Store.

How it works

A local folder holds no secrets, so the path is typed on the node instead of coming from a saved connection. Before any read or write the platform checks two things: whether local FS nodes are enabled at all (a server setting that is off by default, even in development) and whether the path falls inside the list of allowed roots, when one is configured. If either check fails, the node refuses with an explanation rather than quietly working on some other directory.

When exactly one allowed root is configured, the Root path field is filled in for you: it is the only value the check would have accepted anyway.

In production the node is hidden from the palette, but the check lives at run time, not in the palette: hidden is not disabled, and an imported graph refuses just the same.

Common mistakes

• A path from your own machine. The directory resolves where the backend runs — in a typical install that is the filesystem inside a container, not your disk.
• Counting on it in production. A workflow built on a local folder stops running once it moves to production. Switch it to WebDAV before that.
• Expecting the files in the Files tab. That tab shows the workspace store only; a local directory is a separate tree.
• Using local disk as durable storage. It does not survive recreating the container and is not shared between worker replicas: the same node on two replicas sees different content.
• Leaving Root path empty. That is a configuration error and surfaces before the run.

Inputs

—

Outputs

Configuration