> 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/rule-action-split-items.md).
# Rule action: Split items
**Used for:** splitting items that're in a list into separate items.
**Used in:** "THEN"-statements and "ELSE"-statements.
This rule does the exact opposite of the "group items" rule. Select a field of an item that contains a list (for example, a list of available sizes) and create separate items for each element in that list. An item with a list of 5 sizes will be transformed into 5 products that are identical except for the field containing the size.
As shown below, the rule is straightforward to set up. Just make sure the chosen field (e.g. "size") actually contains a list of values — otherwise the rule will not work.
{% hint style="info" %}
Do you want to split your items, but your values are not in a list yet? If you have different values for a field, but instead of a list it's just text, you can use our ["split text to list" rule](/manage-improve-product-data/rules-bulk-edit-and-enrich/how-to-use-actions-then-in-rules/rule-action-split-text-to-list.md) to create a list inside that field.
{% 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/rule-action-split-items.md?ask=&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.