Integrate
Connect translation and measurement to the repositories, applications, and content tools your team already uses.
Your team already stores content in repositories, application databases, CMSs, or translation platforms. An integration connects that existing work to Lingo.dev. It determines which content is read, what starts translation or measurement, and where the result appears.
For translation, the connection sends source content through a localization engine with your saved terminology, instructions, and model configuration. Repository integrations return files; CMS integrations update language versions of content; application code receives data to store or serve. Measurement connections bring in evidence about existing translations while those translations remain in their original system.
Connect the work you already do #
The right starting point depends on where the content changes and who should run the work.
| Starting point | Connection and result |
|---|---|
| Files in a GitHub repository | The GitHub App responds to configured repository events and delivers translated commits through a translation pull request or the source pull request's branch. |
| Files in your own CI pipeline | Run the CLI in GitHub Actions, GitLab CI, Bitbucket Pipelines, or Buildkite. Your job retains artifacts and controls repository delivery. |
| Local files | The CLI submits selected files and retrieves translations into your checkout. You decide when to commit them. |
| Payload collections and globals | Payload translates selected localized fields into the same resources' target locales, manually or after source changes. |
| Zendesk Help Center | Zendesk manually translates selected categories, sections, and articles into their Help Center language versions. |
| Content owned by your backend | The API accepts structured application data. Your code tracks work and stores the returned translations. |
| Translations produced in Crowdin | Crowdin sends supported translation activity for measurement in Radar. The connection does not write corrections back. |
| Translation feedback in Jira | Jira triage examines a labeled issue and proposes changes for review. Repository retranslation requires a separate approval. |
The integration catalog provides complete provider setup and recovery instructions. A CI recipe runs in your infrastructure; it does not create a native account connection.
For agent-driven work, MCP exposes localization operations under the caller's authority. For displaying messages in a React application, use the React library. Message rendering and locale selection remain application responsibilities, even when another connection produces the catalogs.
Follow one change to its destination #
Start with one source change that someone on the team can inspect. A repository might use one checkout message and one target language. A CMS might use one unpublished article. Configure the source selection, target locales, and localization engine, then follow the provider's first-run procedure.
Read the result where it will be used. A file must have the path and structure the application loads. A CMS translation must belong to the intended locale and have the intended publication state. Check its meaning as well as its delivery. Then make one correction and establish where that accepted wording will live, so the next run can treat it appropriately.
Each workflow has its own approval points. The GitHub App can require consent before spending on translation, then deliver a pull request for content review. A CMS connection can write drafts or publish directly. Decide who authorizes the run, who accepts the translation, and who publishes it where those actions occur.
Add measurement where it answers a question #
If the immediate task is understanding existing translations, begin with Measure. Crowdin supplies an event-based connection; CLI scoring checks local catalogs and writes local results. These paths can be used without changing who produces the translations.
Keep the result associated with the text it examined. A finding about an earlier revision may no longer describe the published sentence. Collect translations explains the available evidence intake, and the provider page explains what arrives automatically. Apply any correction through the system that owns the accepted text.