Skip to main content

Connectors

Connectors pull translatable content directly from the systems where it lives and push translations back, removing manual file shuffling.

Connector configuration

Available connectors​

  • TMS platforms — Phrase (Strings), Lokalise, Crowdin, XTM, XTRF, memoQ CMS, Plunet, Lionbridge
  • Code & content repos — GitHub, GitLab, SharePoint, SFTP
  • CMS / commerce — WordPress, Shopify, Adobe Experience Manager, Zendesk

Each connector lives under Connectors in the sidebar with its own configuration page (credentials, project mapping, content selection). Every connector page includes a built-in setup guide walking through the source system's side — where to create the API token, which scopes/permissions to grant, admin consent where applicable. Newer connectors are marked Beta.

Typical flow​

  1. Configure the connector with API credentials for the source system.
  2. Browse and select the content to translate (e.g. a Phrase project, a GitHub branch's locale files, WordPress posts).
  3. Imported content becomes files in a LanguageOps project and goes through the normal translate → QA → review pipeline.
  4. Push the completed translations back to the source system from the same page.
tip

Connector credentials are stored per organisation. If a connector page reports authentication errors after working previously, the source system's token has usually expired — re-enter credentials in the connector's configuration.