Local Text Output
A RocketRide target node that writes pipeline text to files on the machine running the pipeline; choose it when local filesystem output is required instead of an SMB export.
What it does
The node accumulates text for each object and, when the object closes, writes it as a .txt file below the configured output directory. It consumes the text lane and produces no output lane. Choose text_output instead when the destination is an SMB network share rather than the pipeline host’s filesystem.
Lanes
| Lane in | Lane out | Description |
|---|---|---|
text | — | Text content to write to the configured local output directory. |
Configuration
Set the output directory, then decide whether a prefix should be removed from each source path before it becomes the destination-relative path. Most users can leave exclude at its default of N/A.
Destination path
The node reads storePath as the output directory. It resolves this directory and each candidate target path before writing, then rejects a candidate that would resolve outside the output directory. Use an explicit directory the pipeline process is allowed to create and write to; an empty output path causes a warning and the object is skipped.
On Windows, configuration validation rejects storePath values containing < > : " / | ? *. The node also shortens over-long path components before the write and uses extended-length local paths on Windows.
Exclude
The default N/A preserves the complete source path below the output directory. Set a prefix only when that leading source-path portion should not appear in the output hierarchy. If an object path does not begin with the configured prefix, the node logs a warning and skips that object rather than guessing a relative path.
When a prefix is accepted, the node removes it, replaces the source extension with .txt, and creates the necessary directory hierarchy. On Windows, the same invalid-character validation applies to a non-N/A exclude value.
Limitations
This node is unavailable in SaaS deployments and writes directly to the pipeline host’s filesystem. Its filesystem and security capabilities mean the configured output location must be intentionally writable by that process; path traversal outside the resolved output directory is rejected.
Notes
Write behavior
Objects already marked failed upstream are not written. The node writes only non-empty accumulated text in UTF-8. Directory-creation and write failures are logged as warnings and leave the pipeline running; the per-object state is then reset.
Upstream docs
Schema
| Field | Type | Description | Default |
|---|---|---|---|
local_text_output.exclude | string | exclude Which paths to exclude from the output path, if not required put N/A. e.g Users/Downloads/ or N/A | "N/A" |