Input
CSV Smart Reader
Reads a delimited text file and works out the awkward parts itself: the delimiter (comma, semicolon, tab or pipe), whether the first row is a header, and the text encoding.
When to use it
Use it instead of File Input for CSVs from other countries or systems — semicolon-separated European exports, files without a header row, or Windows-1252 and UTF-16 text.
In a pipeline
CSV Smart ReaderType ConversionExport CSV
Settings
| Setting | Type | Required | Default or hint |
|---|---|---|---|
| File Path | text | Yes | e.g. files/export.csv — same places as File Input |
| Delimiter | select | — | auto |
| First row is column names | select | — | auto |
| Encoding | select | — | auto |
| Quote character | select | — | double |
Example
A European export with quoted commas
- File Path=files/eu-export.csv
- Delimiter=Detect
| Line |
|---|
| Name;City;Note |
| Ann;Leeds;"Tea, milk" |
| Bob;Lyon;Coffee |
| Name | City | Note |
|---|---|---|
| Ann | Leeds | Tea, milk |
| Bob | Lyon | Coffee |
The note says what was detected: UTF-8, delimiter ";", first row used as column names.
Worth knowing
- It reads from the same places as File Input — My files, the server, your computer, Google Drive — with $Variables, a * for the newest match, a Loop or an Input Folder.
- Delimiter detection counts , ; tab and | outside quotes on the first lines and picks the most consistent. Pick one yourself if a file is unusual.
- A first row counts as a header when it is text above columns of numbers or dates, or when its labels are all different. Set First row is column names to Yes or No to decide yourself.
- Encoding: a byte-order mark is honoured; otherwise UTF-8, falling back to Windows-1252 when the bytes are not valid UTF-8.
- Run or preview once so the columns are known to the nodes downstream.