Output node
CSV File
Write the incoming rows to a CSV file.
What it does
Writes the incoming rows to a CSV file that you download from the run afterwards. You choose the file name, whether to write a header row, and which character separates the values. CSV is plain text carrying no type information, which is exactly why it travels everywhere. Reach for it when the other side is a spreadsheet, a partner's loader, or a tool you don't control.
Inputs and outputs
| Inputs | One. |
| Outputs | None. This node ends a pipeline. |
When to use it
- Export a finished result as a plain .csv anyone can open
- Produce a tab- or pipe-delimited file a partner's loader expects
- Hand data to a tool that reads CSV and nothing else
Examples
Standard CSV
File: orders.csv · Header row: on · Delimiter: ,
The default, and what almost every tool expects.
Tab-separated
Delimiter: Tab → export.tsv
Safest when your own values contain commas.
Pipe-delimited
Delimiter: |
Common in banking and telecom extracts.
Headerless feed
Header row: off
For a loader that expects data on line 1 and would read a header as a record.
Tips
- Find the file on the run's detail page once the run finishes.
- A Test run leaves you nothing to download: the file is written to the run's scratch space and deleted with it. Press Run for a real file.
- Values containing the delimiter are quoted automatically, but choosing a delimiter your data doesn't use still makes the file easier for the other side to read.
- The delimiter has to be a single plain-ASCII character; anything else stops the run and names the node.
- CSV carries no types, so a code like 00123 loses its leading zeros the moment someone opens the file in a spreadsheet. Write Parquet instead when the types have to survive.