> 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-text.md).
# Rule action: Split text
{% hint style="info" %}
Used for: splitting up the content of a field on a certain character or word, and then using one or more of the parts of the split content.
Used in: "THEN"-statements and "ELSE"-statements.
{% endhint %}
The "split text" rule splits up a field every time a character or word of your choice appears in that field. By using the split text rule you basically cut up a field into several parts. You can then select one or more of these parts to fill a field of your choice.
An example: let's say your descriptions contain the size of your products. You can use the split text rule to fill the "size" field with the part that comes after the word "size:" in your description.
{% stepper %}
{% step %}
### Step: First split — extract everything after "size:"
Use the "split text" rule to split the description on the word "size:" and then select the part that follows it to fill the "size" field.
This will set the size field to the entire second part (everything after "size:").
{% endstep %}
{% step %}
### Step: Second split — refine to just "XL"
If the second part still contains extra text (for example: "XL, other info"), add another "split text" rule on the newly populated "size" field. Split on the comma and select the part before the comma (first part) to get only "XL".
This additional step refines the size field to the exact value you want.
{% endstep %}
{% endstepper %}
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://helpcenter.channable.com/manage-improve-product-data/rules-bulk-edit-and-enrich/how-to-use-actions-then-in-rules/rule-action-split-text.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.