> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/play/catalogue/catalogue-editor/auto-translate.md).

# Auto-Translate

<figure><img src="https://3019081569-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZBycFFNxrdS0X9OsGtmT%2Fuploads%2Fgit-blob-df6ede7b47262771fe2f904bdd1edc05723a420e%2Fimage-20251204-114745.png?alt=media" alt=""><figcaption></figcaption></figure>

The **Auto-Translate** feature allows users to automatically generate translated text for all configured language variants within a catalogue.

It leverages built-in translation models to fill content columns (like `headline`, `subcopy`, or `CTA text`) based on a selected source language row, reducing manual data entry.

#### **How It Works** <a href="#how-it-works" id="how-it-works"></a>

When editing a catalogue that includes a **Language condition column**, users can trigger **Auto-Translate** from the top toolbar.

1. Select the **source cell**, typically the first completed language (e.g., “Play Now” text in a English row).
2. It detects all other rows with language variants (e.g., French, Arabic, Japanese).
3. The system automatically generates translated values for rows that have an empty text value.
4. Translations are inserted into their respective rows in seconds.

{% hint style="info" %}
A Language and Text column are REQUIRED to run Auto-Translate.
{% endhint %}


---

# 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://help.craftsmanplus.com/play/catalogue/catalogue-editor/auto-translate.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.
