Parsing
JSON to Rows
Makes one row per item of a JSON list in a column: an order with three lines becomes three rows, each item's fields as columns.
When to use it
Use it for nested data where one record holds a list — order lines, tags, addresses — and you need a row per list item to total, join or export.
In a pipeline
File InputJSON to RowsSummarize (Multi-Aggregate)Export CSV
Settings
| Setting | Type | Required | Default or hint |
|---|---|---|---|
| JSON column | select | Yes | Select column… |
| Path to the list | text | — | Blank: the JSON is the list. Or e.g. order.lines |
| Keep the other columns on each row | checkbox | — | true |
Example
Order lines as rows
- JSON column=Lines
- Keep the other columns on each row=Yes
| Order | Lines |
|---|---|
| A-1 | [{"sku":"A","qty":2},{"sku":"B","qty":1}] |
| A-2 | [{"sku":"C","qty":5}] |
| Order | sku | qty |
|---|---|---|
| A-1 | A | 2 |
| A-1 | B | 1 |
| A-2 | C | 5 |
Worth knowing
- Path to the list points inside the JSON (order.lines) when the list is not the whole cell.
- Plain items ("red", "blue") go into a Value column; nested objects inside an item stay as JSON text for a JSON Parse further on.
- A row whose list is empty or missing is kept once with blanks, so no record silently disappears.
- The node refuses to make more rows than the server's row limit, before doing any work.
- Run or preview once so downstream column pickers learn the item fields.