> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/actions/data-manipulation-and-transformation/split-text-to-text-collection.md).

# Split Text to Text Collection

Split one text string into a Text Collection in a Salesforce flow, using the delimiter you choose, such as a comma, space or semicolon.

## Overview

This action takes a single text string and splits it into a collection of separate text elements using a delimiter you specify. This helps break down strings like comma-separated values or lists into individual items.

***

## How it Helps

Imagine you have a text string like "apple,banana,cherry" and must work with each fruit individually. This action lets you split the string at the commas, creating a collection containing "apple", "banana", and "cherry" as separate elements.

***

## When to Use It

This action is ideal for:

* **Breaking down lists or comma-separated values.**
* **Extracting individual elements from a combined text string.**
* **Processing data that is structured within a single text field.**
* **Preparing data for use in components that require text collections.**

***

## Example

To split a comma-separated list of colors:

1. **Define the Text Value:** Have a Text variable containing the string "red,green,blue".
2. **Configure the Action:** Specify the Text variable as the "Text Value" and use a comma (",") as the "Delimiter."
3. **Store the Text Collection:** Store the output in a Text Collection variable. You can then use this collection to, for example, display the colors in a picklist.

***

## Key Considerations

* **Text Value:** Ensure you have a valid text string.
* **Delimiter:** Choose the character or string that separates the elements within your text (e.g., comma, space, semicolon)


---

# 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://docs.avonnicomponents.com/flow/actions/data-manipulation-and-transformation/split-text-to-text-collection.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.
