spec sheet · cms & commerce

Prismic and Transglot, bring your documents into translation.

Choose Prismic in your project’s CMS settings, add your credentials, and select the content and languages to sync. Translate and review in one project, then publish to your mapped target languages.

Import into Transglot

Direction: Import into Transglot
Plan: Starter and up
Scope: documents, per custom type, in one repository
Authentication: your repository name and a permanent access token
Get started: Connect from your project’s CMS settings.

Create your project Setup

cms & commerce

the workflow

Connect your content. Review every language.

Connect once, choose your content and languages, then translate and review in the same project. The steps below show how it works in your tool.

Connect Prismic
Choose Prismic in the project’s CMS settings. Add your repository name and a permanent access token.
connect
Choose the content and locale mapping
Select the types and fields you want to localize. The connector reads documents, per custom type, in one repository. Map the source and target locales to your project.
map
Sync and review the translations
Start Sync from CMS to bring the selected source into your project. Translate and review the resulting keys alongside the rest of your project content.
review
Deliver through your project
Pull the translated locale files through the API or CLI, or use the project’s CDN bundle. Prismic remains an import-only source.
deliver

Read translated locale files through the Transglot API, CLI or CDN. Publishing changes back to Prismic is not part of this connector.

what moves

What you can translate and deliver.

Documents come in per custom type from the source language. It stays one way because the Content API is read only and the Migration API can set a document's alternate language only when the document is created, never on one that already exists, so there is no clean per locale slot to write to.

What you can translate and deliver.
Surface	What to expect
Source and scope	documents, per custom type, in one repository
Translated output	Read translated locale files through the Transglot API, CLI or CDN. Publishing changes back to Prismic is not part of this connector.
Keep in mind	Import only. Your original Prismic content is read, and this connector does not write translations back.

get connected

A few steps to your first connection.

Follow your tool’s setup below: add the connection, choose what to sync, and try it with a small set of content. Your team can keep working in the tools they already use.

What you need

your repository name and a permanent access token.

A Transglot project with its source and target locales configured.
Save credentials in the connection settings so your team can work without copying secrets between files.
Hosted API access requires a paid Transglot plan. AI translation uses your workspace’s word allowance.

Create your project

Create a Transglot project with the source and target locales you need.
Open the project’s CMS settings and choose Prismic.
Provide your repository name and a permanent access token.
Save the connection, select the supported content, map locales, then run Sync from CMS.

same project, more possibilities