Browse the docs
Output node

Network Share File

Write the pipeline's output to a Windows network share or a NAS over SMB with a templated path (dates, run id) and a write mode.

Category
Output
Connection
Network Share (SMB)
Also known as
smb, cifs, unc, network drive, mapped drive, windows share, file share, file server, nas, samba

What it does

Writes the pipeline's result straight to a folder on a Windows network share or a NAS over SMB through a saved Connection. You choose the format (CSV, JSON, Parquet or Excel), the destination path, and what should happen if a file is already there. Folders that don't exist yet are created, and the path can carry tokens filled in at run time so a nightly file names itself.

Inputs and outputs

InputsOne.
OutputsNone. This node ends a pipeline.

When to use it

  • Drop a nightly extract where a team opens it from a shared drive
  • Feed a Windows application that imports the files it finds in a folder
  • Publish a dated report every night without hand-editing the name

Examples

Dated file

reports/sales/${date}/orders.csv

${date} becomes 2026-08-26: one file a day, and the folder is created for you.

Per-run file

reports/sales/orders-${run_id}.csv

Every run writes its own file, so a re-run never replaces last night's.

Excel for a team

reports/finance/risk_${date-1:%Y%m}.xlsx · Format: Excel

A workbook people open straight from the share. It is formatted the way Excel Report formats one.

Tips

  • The format settings are the same as on the CSV File, JSON File, Parquet File and Excel File outputs: the delimiter, the JSON layout and the Parquet compression.
  • If it exists: Overwrite replaces the file; Fail stops the run and names the path; Unique suffix writes alongside it with a token added before the extension.
  • Writes happen after a successful Staging or Production run. A Test run never touches the share, so you can press Test as often as you like.
  • Each file is written under a temporary name (.name.trinium-….part) and renamed to its real name only once it has fully arrived, so nobody opens a half-written file. An upload failure fails the run; files that arrived before it stay, and the run's error lists which arrived and which did not.
  • Paths are relative to the Connection's root folder, with forward or back slashes. Missing folders in the path are created, so a ${date} in the middle of a path is safe on the first night.
  • Excel writes a real .xlsx with the same settings as Excel Report: a sheet name, a styled table, columns sized to their content, a frozen header, number formats and a chart. Excel's own limit is 1,048,576 rows per sheet; with Partition by, each folder gets its own workbook.
  • Partition by routes rows into column=value/ folders beneath the destination (which then ends in /), leaving the partition columns out of the files. Replace the folder replaces each folder this run writes into, removing what was there only once every new file has arrived, so a failed run leaves the old files in place.
  • The Connection's account needs permission to create, write, rename and delete files in the folder. A share that requires encryption refuses Trinium for now.