> 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/rule-action-combine-value.md).

# Rule action: Combine value

### Use cases

* Fill or add content to fields with a combination of text or numbers from other fields

Use the **combine value** action to fill a field with contents of other fields and/or a static value of your choice.

### Add colors to product titles to improve visibility

You can use **combine value** to add color and/or size information to the title or the ID of an item. This can improve your item's performance on export channels.

<figure><img src="https://content.gitbook.com/content/u8whzIfip72Kvn3M1bsc/blobs/T3kONf94zPEvl2LrPr09/360007535839" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Important: The condition IF color isn't empty ensures that you only add the "- color" to the title when there is a color available. Otherwise, you would have titles ending with a "-" for the items where the color field is empty.
{% endhint %}

The results are titles with the item color added:

* Durea Instapschoenen 5669 - Taupe
* Teva Sandalen & slippers Kayenta - blue combi

<figure><img src="https://content.gitbook.com/content/u8whzIfip72Kvn3M1bsc/blobs/nPbtwHV3ulYoPimMf9Qs/360007521280" alt=""><figcaption></figcaption></figure>


---

# 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/rule-action-combine-value.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.