> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/manage-improve-product-data/rules-bulk-edit-and-enrich/how-to-use-actions-then-in-rules/item-actions/rule-action-split-items.md).

# Split list into items

Create a separate item for every value in a list field.

Use **`Split list into items`** to create a separate item for each value in a list field.

This action does the opposite of **`Group items together`**. It turns one item with a list of values into separate items.

This action is useful for tasks such as:

* Creating one item for each available size, colour, or other list value.
* Turning grouped product data back into individual items.

Select a field that already contains a list. For example, an item with five values in `size` becomes five items. The new items have the same field values, except each has one `size` value.

The field you select must contain a list. The action cannot split plain text values.

***

## Example `Split list into items` use cases

### Create an item for each size

#### How to build a rule

* Condition: **`For all items`**
* Action: THEN **`Split list into items`**
  * Field to split on: `size`

### Export separate product variants

#### How to build a rule

* Condition: **`For all items`**
* Action: THEN **`Split list into items`**
  * Field to split on: `color`

{% hint style="info" %}

#### Important details

To split text separated by commas, semicolons, or another character, first use [Split text into list](https://helpcenter.channable.com/manage-improve-product-data/rules-bulk-edit-and-enrich/how-to-use-actions-then-in-rules/list-actions/rule-action-split-text-to-list.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpcenter.channable.com/manage-improve-product-data/rules-bulk-edit-and-enrich/how-to-use-actions-then-in-rules/item-actions/rule-action-split-items.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
