> 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/list-actions/rule-action-sort-list.md).

# Sort values in a list

Sort text or numeric values in a list in ascending or descending order.

Use **`Sort list`** to sort the values in a list.

This action is useful for tasks such as:

* Sorting text values alphabetically.
* Sorting numeric values from lowest to highest, or highest to lowest.

Choose ascending order for `a` to `z` or `0` to `9`. Choose descending order for `z` to `a` or `9` to `0`.

***

## Example `Sort list` use cases

### Sort brands alphabetically

#### How to build a rule

* Condition: **`For all items`**
* Action: THEN **`Sort list`** of `brand_list` in `ascending` order

### Show highest values first

#### How to build a rule

* Condition: **`For all items`**
* Action: THEN **`Sort list`** of `price_list` in `descending` order
  * Select **Sort numbers**


---

# 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://helpcenter.channable.com/manage-improve-product-data/rules-bulk-edit-and-enrich/how-to-use-actions-then-in-rules/list-actions/rule-action-sort-list.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.
