> 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-lookup-and-replace-value.md).
# Rule action: Lookup and replace value
### Use cases
* Replace the complete value of a field with another value of your choice. The value will be replaced only if it's an **exact match**.
Use the **Lookup and replace value** action to look for an exact match with a value and only replace it when there is an exact match.
For example, if the lookup value is "Red" and replacement value is "Brick", the output will be "Brick" only for the products that have the exact value "Red". It will not change products that have values like "Dark Red", even though they contain "Red".
### Fill found values
To automatically extract existing values from a field, click **Fill found values**. All the found values will be added to the **When field is equal to** section and then you can add what each value should be replaced with in **Then change value to**.
### Case sensitive
If you select the **Case sensitive** option, it will replace the fields that contain exact values of upper and lower case letters. So if this is active (a check mark will show) and we look for the input "red", and our replacement value is "Brick", the output will be "Brick" for all products that have the value "red", but not for those that have the value "Red".
---
# 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-lookup-and-replace-value.md?ask=&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.