Skip to content
transglot.boardStart free
the boardone contract

connect.

Integrations for every surface your strings live on.

en-US · one contract behind every tile

Wherever your strings already live, the same four gates stand between a draft and a publish. You connect your own account, you set the scopes, and nothing goes back out until it passes.

Start for freeRead a spec sheet
  • your credentials
  • your scopes
  • revoke any time
  • four gates before publish
the switchboard

Forty one integrations, twenty file formats.

41 / 41 pick a tile on the board to read its wiring, its direction and the plan it needs.

Shopify

cms & commerce

Products, collections and pages, read as translatable resources. Shopify stores each secondary locale translation as its own record pinned to a content digest, so publishing reads the current digests and registers against them. The primary locale is never registered.

what syncs
products, collections and pages, per store
what you need
an Admin API access token from a custom app on your store
two wayStarter and up
Open the spec sheet
full wiring diagram inside
the handshake

One contract, behind every connector.

what integrated means here, and the three promises that do not vary by connector
  • yours, not ours

    Your credentials sign in. Your scopes set the ceiling.

    You authorise into your own account, and the connector can never reach past what you granted. Revoke it and it goes dark the same second, with no shadow copy left behind.

  • gates everywhere

    A CMS draft meets the same four gates as code.

    Placeholders, plurals, glossary and length are checked on every row before anything is allowed back out, whatever surface the row came from.

  • honest arrows

    Two way means the round trip. Import only says so upfront.

    Nine tiles read import only, and each one names the reason: a read only API, a single language record, a write path that does not exist yet. Each flips the day that changes.

missing one?

The next connector is the one you ask for.

the catalogue is not finished, and the next connector is usually the one somebody asked for

FAQs

What teams ask before they connect the first one.

Do integrations cost extra?
No. All 41 are included in your plan and none of them is billed as an add-on. 36 are available from Starter; the 5 repository and issue apps (GitHub, GitLab, Bitbucket, Azure Repos, Jira) need Team.
32 write reviewed translations back to the tool they came from, so the connector is the round trip rather than half of it. The other 9 import only, and the catalogue says which is which before you connect one rather than after.
Two ways in without a connector. All 20 native file formats go in through the browser upload, the API or the CLI, and the reviewed files come back out through the pull endpoint, the CLI, the CDN bundle or a file storage sync. And the REST API plus signed webhooks are the same interface the connectors themselves use, so a bespoke one is a normal integration rather than a special case.
Not for the CMS and design connectors: you authorise the tool, pick the project and the locales, and the first sync runs. The repository apps ask for the branch and the file paths your strings live at, which is usually a developer answering one question rather than doing a piece of work.
Yes, and by the same gates. Placeholders, plurals, glossary and length are checked on every row before anything is allowed back out, whatever surface the row came from. A connector is a way in and out, never a way around the checks.
The next sync sees the source has moved and marks every translation of that string stale rather than leaving a confident old translation in place. Stale rows are re-translated and re-checked; approved rows a human signed off are never overwritten by the machine.
works with what you already run

41 connectors, already built.

All 41 integrations
your credentials · your scopes · revoke any time

Patch in your first surface. The gates come with it.

Start for freeRead the Shopify spec sheet
no card to start · connectors run from Starter · the five repository and issue apps need Team