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

# Crowdin

<div align="left"><figure><img src="/files/jkpur7ZjQ97BjfQ1IYO0" alt=""><figcaption></figcaption></figure></div>

## Set up

### Navigate to the Integration settings view

1. Select an app in the top left corner from the Switcher
2. Navigate to **App Settings** by clicking the gear icon (⚙️) at the top of the Timeline sidebar
3. Click on **Integrations** in the sidebar

### **Connect Crowdin**

1. Find the **Crowdin** integration module under the **Translations** section.
2. Click the **Connect** button.
3. Enter a Crowdin API token.

{% hint style="info" %}
You can find or create a new Crowdin API token by visiting your Settings > API page in the Crowdin dashboard. Note that the API token must have the following grants:

* Projects > Projects (List, Get, Create, Edit) - **Read / Write**
* Projects > Translations status **- Read**
* Projects > Source files & strings **- Read**
* Projects > Webhooks **- Read**
* Projects > Translations **- Read / Write**
  {% endhint %}

### Configure the Crowdin integration

1. Choose a Crowdin **Project** from the dropdown. All translations in this project will be pulled into Runway and cross referenced with your app's codebase.
2. If your team uses Crowdin Enterprise, enter the enterprise subdomain. This is the subdomain in the URL that you use to access your Crowdin Enterprise account.

For more details on how the translations integration populates the data found on the Translations step, visit the [Translations step documentation](/using-runway/release-steps/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.runway.team/integrations/translations/crowdin.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.