Split Out

Node catalog Transformations
On this page

Turn a list inside item(s) into separate items

Usage and specifics

Use Split out when an item contains a nested list that should become rows. This node builds a list in items; it does not automatically run an action for every row. Add a loop for that.

With this manual input:

json
{
  "records": [
    { "id": "record-1", "tags": ["urgent", "review"] }
  ]
}

Set source to input.records, field to tags, then enable includeNoOtherFields. Output contains:

json
{
  "items": [{ "tags": "urgent" }, { "tags": "review" }],
  "count": 2
}

With includeNoOtherFields disabled, other parent fields are preserved. A primitive value is placed in value; a child object is merged at parent level and may replace same-named fields. Check this shape before mapping later steps.

source identifies parent items; field identifies the list inside each one. If that field is not a list, the item produces no rows. An incorrect source can therefore give empty output without an error.

Technical type : split_out. Runtime : nodulz.

Credentials and prerequisites

This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.

See the credentials guide if a remote source or execution target requires access.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter Type Default Values / limits
source string "" -
field string "" -
includeNoOtherFields boolean false -

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json
{
  "source": "",
  "field": "",
  "includeNoOtherFields": false
}

Verification

Check both example rows, then test tags: [] and an item without tags: neither should produce rows. Toggle includeNoOtherFields and inspect the child value and parent identifier paths. Do not reuse the same mapping path without checking this option.

See also : Expressions and data, Executions, Node catalog.