Connect DatoCMS
Import DatoCMS records into transglot and write reviewed translations into each localized field's target-locale slot.
| Direction | Two-way |
| Imported | The source-locale value of the localized fields you map, on the models you choose |
| Written back | Each field's target-locale slot. The source locale and every other locale are kept |
| Sync | Sync from CMS |
| Plan | Starter and above |
Before you start
- Mark the fields you want translated as localized in each model.
- Enable your target locales in the project's locale settings. DatoCMS locale codes must match the language codes in your transglot project.
- Create an API token with read and write access to your records in the project's API token settings.
Connect
Open your project's settings, choose CMS, and pick DatoCMS in the CMS list. There is no URL to type: the API token identifies the project.
| Field | What to enter |
|---|---|
| API token | The token you created |
| Content types | Model IDs (or model API keys), comma separated |
| Translatable fields | Localized field API keys, comma separated |
| Publish these locales | The target locales to write back |
Select Connect, then Test connection. A successful test names the project.
What gets imported
For each record of each model, transglot reads the source-locale value of every mapped localized field and imports the ones that hold text.
How translations are written back
DatoCMS treats a localized field's value as a whole, so writing one locale on its own would drop the others. transglot reads the record's current field values, adds the target-locale values, and writes the merged field back. The source locale and every other locale keep their values.
Troubleshooting
... the credentials were rejected.The token is wrong, revoked, or read-only.... the model or record was not found, check the settings.Check the model IDs in Content types.... DatoCMS rejected the write, check the field/locale mapping.A mapped field is not localized, or a target locale is not enabled in the project.