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

# Localization

Localization Steps connect your AirOps workflows with translation and localization platforms, enabling automated multilingual content workflows. These integrations allow you to streamline the translation process, manage localized content at scale, and maintain consistency across different language versions.

The Localization Steps include:

1. [**Crowdin**](/integrations/overview/localization/crowdin.md) -- manage translation projects and sync content with Crowdin's localization platform

Localization integrations transform how you manage multilingual content by bridging the gap between AI-powered content generation and your translation management systems. These connections allow you to automate the localization workflow from content creation to translated delivery.

With Localization Steps, you can build workflows that automatically send generated content for translation, sync translations back to your content management systems, manage translation memory and glossaries, and coordinate multilingual content updates across your digital properties.

{% hint style="info" %}
Note: Localization Steps are designed for Workflow applications. Authentication requires appropriate permissions for each respective platform.
{% 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://docs.airops.com/integrations/overview/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.