Connect Storyblok
Import Storyblok stories into transglot and write reviewed translations back into each story's field-level translation keys.
| Direction | Two-way |
| Imported | The base (source) value of the fields you map, on stories whose content type you choose |
| Written back | Each field's __i18n__ key for the target language. The base field is never written |
| Sync | Sync from CMS |
| Per sync | Up to 1,250 stories per content type |
| Plan | Starter and above |
Before you start
- In the component schema, mark each field you want translated as translatable (field-level translation).
- Enable your target languages in the space settings. Their language codes must match the language codes in your transglot project.
- Create a personal access token in your Storyblok account settings.
Connect
Open your project's settings, choose CMS, and pick Storyblok in the CMS list.
| Field | What to enter |
|---|---|
| Space ID | Your numeric space ID, from the space's general settings |
| Region | The data region your space is hosted in: EU, US, AP or CA |
| Personal access token | The token you created |
| Content types | The component names of the stories to import, comma separated |
| Translatable fields | Field names, comma separated |
| Publish these locales | The target languages to write back |
Select Connect, then Test connection. A successful test names the space.
What gets imported
For every story whose content type is one you listed, transglot reads each mapped field from the story's top-level content. The base field (for example content.title) is the source. Fields with no text are skipped.
How translations are written back
Storyblok stores a field-level translation as a separate key next to the base field: content.title__i18n__fr for French. transglot reads the story, sets those target-language keys for the mapped fields, and saves the story. The base field and any content transglot does not manage are kept as they were.
transglot saves the story but does not publish it in Storyblok. Publish the story when you want the translations live.
Troubleshooting
... the credentials were rejected.The personal access token is wrong or revoked.... the space or story was not found, check the settings.Check Space ID and Region.- A story is not imported: check its content type is in Content types and the mapped fields are text fields at the top level of the story.