Integrations
Connect repository and CMS translation, run localization in CI, collect Crowdin evidence, or investigate Jira feedback.
Use Lingo.dev alongside the tools where your team writes, translates, and reviews content. Each connection has a different job. Some return translated content to its source system; others collect evidence or help investigate feedback.
Translate content in its existing system #
These native connections read selected source content, translate it with a localization engine, and write the result back using the provider access you grant.
| Connection | What starts the work | Where translations return |
|---|---|---|
| GitHub | Configured repository events or a scoped translation command | A translation pull request for default-branch changes, or commits to an eligible pull request's branch. |
| Payload | Manual Sync or source-change notifications from the plugin | Localized fields on the same collections and globals, under the selected target locales. |
| WordPress | Manual Sync or published saves notified by the plugin | The linked Polylang or WPML translation of each post, in the selected languages. |
| Zendesk Help Center | Manual Sync | Language versions of selected categories, sections, and articles. |
Provider setup decides what each connection translates. For GitHub, select repositories and source-file patterns. For Payload, select collections and globals with localized fields. For WordPress, select post types. For Zendesk, select categories, sections, and articles separately: selecting a category does not select its children.
Publication behavior also belongs to the provider. Payload's Publish mode does not write to a published document with unpublished edits until they are published or reverted, since publishing the translation would release them. A Zendesk draft write can remove an already-live locale version until it is republished. Read the provider's publication section before the first write, especially when translations already exist.
Run translation inside your pipeline #
GitHub Actions, GitLab CI, Bitbucket Pipelines, and Buildkite run the CLI in your own runner. The recipes start with downloadable artifacts or a single trusted branch so you can inspect the result before widening repository write access. With .lingo/lock.json committed, lingo check fails a pull or merge request when a source changed since its last translation or a target file is missing. It needs no API key.
Your pipeline owns scheduling, secrets, output retention, and commit or pull-request creation. The Lingo.dev API key authorizes translation; the provider credential authorizes repository writes. Automate translations in CI develops the process for keeping source revisions, completed output, and application checks together.
Measure translations or investigate feedback #
Crowdin sends supported string-level activity into Radar. Use it to examine translations produced in Crowdin without moving their generation or review workflow. Configure a measurement for the question you want answered, then inspect the collected text and its result. This connection does not synchronize corrected translations back to Crowdin.
Jira starts from a reported problem. Adding the lingo label asks the triage workflow to examine the issue and propose glossary, rule, or brand-voice changes. People apply or dismiss each suggestion, then choose whether to retranslate affected connected content. Jira triage does not translate the contents of the ticket as a localization project.
Complete the first run before expanding scope #
Each provider page carries a small first run through authorization, configuration, output inspection, and recovery. Use that run to establish what the connection reads and changes. Connection availability can depend on organization permissions and feature access; a provider credential alone does not grant access to a localization engine.
When retiring a connection, stop new triggers and deal with provider credentials separately. Disconnecting does not reverse delivered content, posted comments, or recorded measurements. The provider's recovery section explains what state remains and what a reconnect will do.
For an application-owned workflow, continue with DevTools for the API, CLI, and JavaScript interfaces.