The Split Out node takes an array field inside a single item and fans it out into multiple items -- one per array element.
The Split Out node takes an array field inside a single item and fans it out into multiple items -- one per array element. This is essential when an API returns a batch response and you need to process each element individually downstream.
Real-world example: A blog CMS returns a post object with a comma-separated tags string. You need individual items per tag to upsert each tag into a taxonomy database table.
// Incoming item:
{
"post_id": 42,
"title": "Getting Started with n8n",
"tags": "automation, n8n, workflow, no-code"
}
```text
First, use an Edit Fields node to convert the string to an array:
```text
tags_array = {{ $json.tags.split(',').map(t => t.trim()) }}
```text
Then configure the Split Out node:
| Setting | Value |
|---------------------|---------------|
| Field To Split Out | `tags_array` |
| Include Other Fields| Enabled |
```json
// Output — 4 separate items:
{ "post_id": 42, "title": "Getting Started with n8n", "tags_array": "automation" }
{ "post_id": 42, "title": "Getting Started with n8n", "tags_array": "n8n" }
{ "post_id": 42, "title": "Getting Started with n8n", "tags_array": "workflow" }
{ "post_id": 42, "title": "Getting Started with n8n", "tags_array": "no-code" }
```text
Each item retains the parent fields (`post_id`, `title`) while isolating a single tag for downstream processing like database upserts or API calls per tag.
**Related:** [Flatten Deeply Nested API Responses](../code-node-mastery/01-flatten-deeply-nested-api-responses.md) | [Use the HTTP Request Node as a Universal Connector](../integration-patterns/01-use-the-http-request-node-as-a-universal-connector.md)
I build production n8n and Cloudflare automation for teams — the same engineering behind HarperFlow. Fixed-price, escrow-protected, US-based.