Connect Contentstack
Import Contentstack entries into transglot and write reviewed translations into each entry's target-locale version.
| Direction | Two-way |
| Imported | The source-locale version of the fields you map, on the content types you choose |
| Written back | Each entry's target-locale version. The source locale is never written |
| Sync | Sync from CMS |
| Plan | Starter and above |
Before you start
- Add your target languages to the stack. Contentstack locale codes must match the language codes in your transglot project.
- Create a Management Token with read and write access in the stack's token settings.
- Note the stack API key from the stack settings. It identifies the stack and is not a secret.
Connect
Open your project's settings, choose CMS, and pick Contentstack in the CMS list.
| Field | What to enter |
|---|---|
| Data-hosting region | Your stack's region: AWS-NA, AWS-EU, AWS-AU, AZURE-NA, AZURE-EU, GCP-NA or GCP-EU |
| Stack API key | The stack API key, for example blt0123456789abcdef |
| Management token | The Management Token you created |
| Content types | Content type UIDs, comma separated |
| Translatable fields | Field UIDs, comma separated |
| Publish these locales | The target locales to write back |
Select Connect, then Test connection. A successful test names the stack.
What gets imported
For each content type, transglot lists the entries in your source locale and imports the mapped fields that hold text. Each entry's title becomes the description on its keys.
How translations are written back
Contentstack keeps a separate version of an entry for each locale. For each target locale, transglot reads that locale's version, replaces only the mapped fields with the reviewed values, and saves it. Saving a target locale for the first time localizes the entry into that locale. Every other field is kept as it was, and the source-locale version is never addressed.
transglot saves the localized entries but does not publish them. Publish in Contentstack when you want the translations live.
Troubleshooting
... the credentials were rejected.The Management Token or stack API key is wrong, or the token lacks write access.... the stack, content type or entry was not found, check the settings.Check Data-hosting region, Stack API key and the content type UIDs.... Contentstack is rate-limiting the request, retry.Wait and run the sync or publish again.