> 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/text-actions/rule-action-split-text.md).

# Split text and keep a selected part

Split a field at a character or word, then use the resulting parts.

Use **`Split text`** to split a field at a character or word, then save one or more parts in another field.

This action is useful for tasks such as:

* Extracting a product attribute from a description.
* Separating multiple values stored in one text field.

### Choose which split part to keep

When **`Split text`** finds the split text, it separates the field value into parts. In the first example, splitting on `size:` creates one part before `size:` and one part after it. Selecting `second` saves the part after `size:` in `size`.

Choose a position based on where the value appears:

* Select `first` through `twentieth` to count parts from the beginning of the field value.
* Select `last` through `fifth last` to count parts from the end of the field value.

***

## Example `Split text` use cases

{% hint style="info" %}

#### Tip

You can use more than one **`Split text`** action to refine a result.
{% endhint %}

### Extract a size from a description

#### How to build a rule

* Condition: **`For all items`**
* Action: THEN **`Split text`** in `description`
  * Split on `size:` and keep `second` until `second` and store in `size`

### Keep only the size value

#### How to build a rule

* Condition: **`For all items`**
* Action: THEN **`Split text`** in `size`
  * Split on `,` and keep `first`


---

# 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/text-actions/rule-action-split-text.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.
