Split Out

Turn a list inside one item into separate items, so the next nodes handle each entry on its own.

Try it

workflow · save-links-to-sheet.awf 4 étapes

Save All Page Links to Sheet : un workflow de 4 étapes, qui commence par When Started et se termine par Add a row per link.

1. 1 When Started(Déclencheur — ouvrir sa page de documentation) Déclencheur
2. 2 Collect all links(Get All Link — ouvrir sa page de documentation) Get All Link
3. 3 One link per row(Split Out — ouvrir sa page de documentation) Split Out
4. 4 Add a row per link(Google Sheets — ouvrir sa page de documentation) Google Sheets

Ouvrir dans AWFlow Copier le .awf

What it does

Split Out reads the list in Field To Split Out and sends one item per entry. Each new item holds the entry under one field: Output field name if you set it, otherwise the last part of the path. Splitting tags with Output field name tag turns { "tags": ["a", "b"] } into { "tag": "a" } and { "tag": "b" }.

Entries are always wrapped this way, even when they are objects, so a result object ends up under { "result": { ... } }.

With Include Other Fields on, the item’s other top-level fields are copied onto every new item. That is how each entry keeps track of where it came from, for example an order id next to each order line.

If the field holds a single value instead of a list, you get one item. An empty list gives no items.

When to use it

• An API returns one item with a results list, and you want the next nodes to run once per result.
• Turn a tags or emails list into items you can Filter, Sort or send one by one.
• Expand order lines while keeping the order’s id and date on each line.
• If you want the entries passed on as they are (not wrapped in a field), use Pick Field instead.

Inputs and settings

Réglage	Type	Ce que cela fait
Field To Split Out OBLIG.(obligatoire)	Text	The path to the array field to split out (without the node name or id).
Output field name	Text	The name of the field each element is placed under. Defaults to the field being split out.
Include Other Fields	Toggle	Whether to carry the remaining input fields onto each output item. Par défaut : Off

Write Field To Split Out as field names joined by dots, starting from the incoming data: results or data.results, not $input.results.

Include Other Fields removes the whole top-level field the path starts in. Splitting data.results drops everything under data, not just results.

Outputs

• Output

One item per list entry. Read an entry downstream with {{ $input.tag }} (using your output field name), or {{ $input.result.title }} when the entries are objects.

Dependencies and credentials

None. This node needs no connection and has no slots for other nodes.

Example workflow

1. An Http Request node returns { "orderId": 42, "lines": [ { "sku": "A1", "qty": 2 }, { "sku": "B7", "qty": 1 } ] }.
2. Split Out with Field To Split Out lines, Output field name line and Include Other Fields on. You get two items, each with orderId and line.
3. A Google Sheets node (Data, Append Values into Worksheet) adds the lines to your sheet, reading {{ $input.orderId }}, {{ $input.line.sku }} and {{ $input.line.qty }}.

Common issues

• “Field “…” does not exist in the input object”. The path does not match the incoming data. The message shows the data the node received: check the spelling and upper and lower case.
• Only one item comes out. The field holds a single value, not a list. Point the path at the list itself.
• No items come out. The list is empty, so there is nothing to split.
• “No source node is connected to this node.” Connect the node that produces the data to Split Out’s input.

Related nodes

• Pick Field: keep one field, passing objects through as they are.
• Aggregate: the reverse, gather many items back into one list.
• Limit: keep only the first few entries.
• Split in Batches: work through the items a batch at a time.