# Split

The **Split** component breaks a dataset into smaller, structured pieces that you can process independently in subsequent flow steps. Use it when a connector returns a large table or complex object and you only need specific portions — such as selected columns, targeted attributes, or filtered sections. While [Aggregate](/flow-setup-essentials/designing-a-flow/flow-transformation/aggregate.md) combines multiple items into one output, Split does the opposite: it divides a single dataset into separate branches.

### **Use Case Example**

Imagine you have a Google Sheet storing thousands of rows of product data (Name, Category, Price, Stock, etc.). You only want to extract **specific columns**, for example, **Category and Price**, to send into another system (like an AI step, analytics tool, or external API).

Instead of passing the entire sheet, the **Split** feature lets you carve out only the fields you need.

Using **Includes Only**, you can split the dataset so only the selected fields move forward, simplifying your next steps and making your flow more efficient.

### Step 1: Add a Connector

* Start your flow by adding a connector that contains the data you want to split.

Add a ***Google Sheets*** Connector and select the action ***getDataFromSheet***.

<figure><img src="/files/ZvM4tj7t9u9R3aIbgBuq" alt=""><figcaption></figcaption></figure>

* This step retrieves all the data from your sheet and provides it as the output for the next steps.

### Step 2: Add the Split Transformation

* After your connector step, click the '+' button to insert a new step.
* Search for **Flow Transformation Actions** and select **Split**.

<figure><img src="/files/ev95HLxsb3SGI0dpch4H" alt=""><figcaption></figcaption></figure>

* The Split step divides the data based on the input field and strategy you choose. Configure the Split step as follows:

**Fields To Split Out**

{{steps.getDataFromSheet.output}}

<figure><img src="/files/J94qiDlKQAL2Wi223ApN" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
*This references the output from the previous connector step.*
{% endhint %}

**Split Out Strategy**

The **Split Out Strategy** lets you decide whether to include only certain fields or exclude certain fields.

As an example, we will choose the *Includes Only* Strategy in this scenario.

{% hint style="info" %}
You can choose Includes Only or Excludes Only, depending on your use case.
{% endhint %}

<figure><img src="/files/O0HFqcmqz5cXSaUGM82O" alt=""><figcaption></figcaption></figure>

**Input Fields**

You can select any input field you want to use for splitting, like the Major Dimensions of the data from the sheet, in this case.

<figure><img src="/files/Nr2aiSo3pO9K3IqwSXrV" alt=""><figcaption></figcaption></figure>

Save the step.

<figure><img src="/files/DiiuGa0pOo344941YmQb" alt=""><figcaption></figcaption></figure>

### Step 3: Testing the Split Step

You can test the split step to ensure it works as expected:

* Test the step directly from the **Test** inside the Split step.

<figure><img src="/files/a64ccDyyKSewgdQxGiTF" alt=""><figcaption></figcaption></figure>

* Next, test the entire flow from the **Test** button at the top-right corner of the flow editor.

<figure><img src="/files/71mM91hKjTMN5F8fiZXV" alt=""><figcaption></figcaption></figure>

### Using Split Data

Once the split step is configured, the resulting data can be used in further steps of your flow.

For Example:

* Passing specific fields to another connector for processing.
* Filtering the dataset based on certain dimensions before performing calculations.
* Using split data as input for AI agents or custom code steps.


---

# Agent Instructions: 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:

```
GET https://docs.fastn.ai/flow-setup-essentials/designing-a-flow/flow-transformation/split.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
