> 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-conversion-and-formatting/format-text-collection.md).

# Format Text Collection

## Overview

This action allows you to easily standardize the format of text values within a collection. You can apply various formatting operations, such as converting to uppercase, lowercase, or escaping special characters for different contexts (like CSV or HTML).

***

## How it Helps

Imagine you have a collection of user-entered comments with inconsistent capitalization. This action lets you quickly format all the comments to lowercase, ensuring a consistent presentation.

***

## When to Use It

This action is ideal for:

* **Standardizing text formats within collections.**
* **Cleaning up user-entered data.**
* **Preparing data for integration with other systems or components.**
* **Automating text formatting tasks within your flows.**

***

## Example

To format a list of product names for a CSV file:

1. **Create a Text Collection:** Have a Text Collection variable containing a list of product names.
2. **Configure the Action:** Select the product name collection and choose "Escape CSV" as the operation to ensure that any special characters in the names are properly escaped for CSV compatibility.

***

## Key Considerations

* **Source Collection:** Ensure you have a valid collection of text values.
* **Operation:** Select the desired formatting operation (e.g., uppercase, lowercase, escape HTML)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.avonnicomponents.com/flow/actions/data-conversion-and-formatting/format-text-collection.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.