> For the complete documentation index, see [llms.txt](https://docs.hexabot.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hexabot.ai/localization.md).

# Localization

Manage supported languages, fallback behavior, and translations for multilingual workflows.

Hexabot helps you run multilingual workflows from one workspace.

You can define supported languages, set a default language, and manage translations in one place. This lets the same workflow serve users across channels in the language that fits them best.

### What localization includes

* **Languages** — add the languages your workspace supports.
* **Default language** — choose the fallback language for your workflows.
* **Translations** — translate user-facing content such as messages, labels, and buttons.
* **Automatic language handling** — use the user’s language when it is available.
* **RTL support** — support right-to-left languages such as Arabic and Hebrew.

### Why it matters

* Reuse the same workflow across multiple languages.
* Keep translated content organized in one place.
* Deliver a more consistent experience across channels.

### In this section

* [Languages](/localization/languages.md)
* [Translations](/localization/translations.md)


---

# 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://docs.hexabot.ai/localization.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.