Skip to main content

​
What It Does

  • Splits rows based on a selected column containing lists or multi-value arrays
  • Each list item becomes its own row — all other columns are preserved
  • Designed for lead enrichment, pipeline hygiene, or flattening JSON-like structures
  • Supports arrays or comma-separated fields already parsed as lists
  • Download-ready output in both CSV and Parquet
🔄 Whether you’re flattening tech stacks or cleaning up tags, this node helps normalize list-based columns into usable rows.

​
🏁 Getting Started

Split Data node configuration
1

Add the Node

Drag in the Split Data node from your toolbox.
2

Choose a Column to Split

Select a column from the dropdown that contains lists or array-like data.
3

Run the Node

Each list item will become its own row — with all other data intact.

​
Inputs

​
🛠️ Required Fields

  • Column to Split (✅)
    Select a column with list-style values to explode into multiple rows.
    Why it matters: This controls which field is broken apart and normalized.

​
Output

A new dataset with exploded rows:
  • Every list item becomes its own row
  • All other fields are duplicated across the new rows
  • Output available in CSV and Parquet formats

​
How It Works

  1. Loads input dataset and parses the selected list column
  2. Validates that the field contains actual list values
  3. Uses row explosion to generate one row per list item
  4. Preserves all original columns and values
  5. Returns a clean, flattened table

​
🚀 Example Use Cases & Prompts

Use CasePrompt or Setup Example
Break out tags or labelsSplit the tags field
Normalize tech stacksExplode the technologies_used
Unpack product bundlesUse the products list column

​
✨ Pro Tips

Use Split before grouping, filtering, or routing — especially when mapping rows to reps, tags, or products.
Want to split more than one column? Just chain another Split Data node — one per field.

​
⚠️ Important Considerations

The column must contain valid list-like data — if it’s not already a list, use upstream nodes to reshape it.
Empty or null lists are automatically skipped — they won’t produce any rows.

​
🛠 Troubleshooting & Gotchas

SymptomLikely CauseQuick Fix
Nothing splitsSelected column isn’t a listCheck formatting — upstream transform may be needed
Output is blankLists were null or emptyClean your data or apply filters first
“Column not found” errorColumn was renamed or droppedRe-select the correct column

​
📝 FAQ

Only if the values have already been parsed into actual lists. Use a transform step if they’re still plain strings.
They’re duplicated across all new rows to keep the dataset structure consistent.
Not yet — but you can use multiple Split Data nodes, one per column.

​
💰 Pricing

The Split Data node is free — no credits required.

Clean structure, clean plays. Split your lists and turn complexity into rows you can actually work with.