> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/data-management/workbench/model-data/flow-models/flow-steps/group.md).

# Group

## What does it do?

It groups rows that have the same values into one group or bucket, and is used in conjunction with aggregate functions (`COUNT`, `SUM`, `MIN` or `MAX`) to output additional summary columns.

## How to use it ?

On any previously steps available in your editor select a step and click on **Group**

<figure><img src="https://34758050-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MC1g4I2_CgXd0qAq1P7%2Fuploads%2FDcC4Ca8pKA5LYD4BuTRu%2FScreen%20Cast%202022-09-21%20at%2012.51.20%20PM.gif?alt=media&amp;token=e435dab0-c054-4619-aee8-e4581fcc4343" alt=""><figcaption></figcaption></figure>

## How to configure it ?

<figure><img src="https://34758050-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MC1g4I2_CgXd0qAq1P7%2Fuploads%2FLBA3SvRrlrhMFrBckOru%2Fimage.png?alt=media&amp;token=d77cead1-70d6-4da8-b69e-7969b9d2fa45" alt=""><figcaption></figcaption></figure>

#### Group on

In the group by form, start by selecting the columns you want to group on. The grouping will be applied as the unique values generated by the selected columns.

{% hint style="info" %}
Columns not used in the "grouped on" will not be available in the output of this step.
{% endhint %}

#### Aggregation (optional)

You can then optionally create as many aggregation as you need. An aggregation takes :&#x20;

* An operator (`COUNT`, `SUM`, `MIN` or `MAX)`
* A column to perform the aggregation on. The column must be of numerical type.
* A new column name for the aggregated data you will create.


---

# 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.whaly.io/data-management/workbench/model-data/flow-models/flow-steps/group.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.