# Common Manipulator Options

The following manipulator options are listed for every manipulator. However, each manipulator may or may not support the common manipulator option. Or they may have special rules for the common manipulator options. Check each manipulator for additional details on how they handle the common manipulator option.

## applyToLanguages

A text value.

Determines which languages the manipulator should apply to. A comma can be used to separate multiple languages. If no languages are provided, all languages will be manipulated.

The ID of each language should be used for each language the manipulator should be applied to.

#### Supported Manipulators

* Add-Replace-Field
* File-To-Text
* Markdown
* Regex
* Relationship
* Tidy

#### Working with Languages and Manipulators

When a specific language requires a manipulator you can this option with the ID of that specific language. If multiple languages require the same manipulator config, a comma separated list of language IDs can be provided.

When multiple language IDs are provided, the manipulator will apply its configuration to every content with those languages.\
So, if the manipulator adjusts the value of a specified field, the field for each language specified will be run through the manipulator with the set config individually.\
And, if the manipulator adds or replaces a specified field, that field will be added/replaced for each language specified.

As such, be aware, if a different value is required for different languages, then you will (often) need to create multiple manipulators with appropriate config for each language. i.e., The regex on the same field for each language is different. Then a manipulator for each language may be required. Or if a liquid template specifies values for a specific language to parse and apply to, the field may need to be added to that specific language.


---

# Agent Instructions: 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:

```
GET https://motivlabs.gitbook.io/impulse-user-manual/content-manipulators-motators/common-manipulator-options.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.