> For the complete documentation index, see [llms.txt](https://docs-v3.toucantoco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-v3.toucantoco.com/data-management-in-datahub/datasets-in-toucan/preparing-data/overview-of-youprep-tm/text/split-column.md). # Split column The Split column step allows to split a text column into several columns, based on a delimiter. ### Step parameters * `Split column...` **column(string)\*:** the column to plit. msut be a column containing string characters. * `Delimiter` **string\***: a character or a string of characters that will be identified as delimiter to split the column. Can be a string of any length * `Number of columns to keep` **int\***: the number of columns to keep after splitting the original column. Starting from the first chunk ### Example **Input**

Split column - input

**Configuration** ```json { "column": "email", "delimiter": "@" "number_cols_to_keep": 2 } ``` **Output**

`Text - Split column output

{% hint style="info" %} The original column remains intact while the split results are written in specific columns automatically named after the original column name (in the form `original_column_name_1`, `original_column_name_2` etc.). --- # 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-v3.toucantoco.com/data-management-in-datahub/datasets-in-toucan/preparing-data/overview-of-youprep-tm/text/split-column.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.