> 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/manage-product-and-improve-data-es/reglas-edicion-masiva-y-enriquecimiento/how-to-use-actions-then-in-rules/acciones-de-texto/rule-action-maximum-length.md).

# Recortar el texto hasta un límite de caracteres

Recorta los valores de texto para ajustarlos al límite de caracteres de un canal.

utilizza **`Trim Testo`** A acortar el valor de un campo A un máximo de Numero di caracteres.

Esta acción es útil para tareas como:

* Cumplir los límites de caracteres del canal para campos como `title`.
* Mantener las palabras completas cuando un campo truncado debe seguir siendo legible.

***

## Ejemplo `Trim Testo` casos de utilizza

{% hint style="info" %}

#### Consejo

Elige **taglia direttamente** A fin de cortar el Testo en el límite de caracteres.

Elige **taglia in base alle parole** A fin de conservar la palabra completa que quede en ultimo lugar dentro del límite.
{% endhint %}

### Limita los títulos de los productos A 30 caracteres

#### Cómo A crear la Regola

* Condición: **`Para todo Articoli`**
* Acción: allora **`Trim Testo`** di `title` limitar A `30` caratteri e `taglia direttamente`

### Mantén las palabras completas In los títulos acortados

#### Cómo A crear la Regola

* Condición: **`Para todo Articoli`**
* Acción: allora **`Recortar Testo`** di `title` limitar A `15` caratteri e `taglia in base alle parole`

### Limita las descripciones de los productos a 500 caracteres

#### Cómo A crear la Regola

* Condición: **`Para todo Articoli`**
* Acción: ALLORA **`Recortar texto`** di `description` limitar A `500` caratteri e `taglia in base alle parole`


---

# 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/manage-product-and-improve-data-es/reglas-edicion-masiva-y-enriquecimiento/how-to-use-actions-then-in-rules/acciones-de-texto/rule-action-maximum-length.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.
