Content platforms
Connect Webflow
Import Webflow CMS collection items into transglot and write reviewed translations into each item's secondary-locale variants.
| Direction | Two-way |
| Imported | The primary-locale value of the fields you map, on the collections you choose |
| Written back | Each item's secondary-locale variant. The primary locale is never written |
| Sync | Sync from CMS |
| Plan | Starter and above |
Before you start
- Add your target locales to the site in Webflow's localization settings.
- For each existing item, add its secondary-locale variants in the CMS. The Webflow API can update a locale variant of an existing item but cannot create one.
- Create a site API token with CMS read and write access in your site's settings.
Connect
Open your project's settings, choose CMS, and pick Webflow in the CMS list.
| Field | What to enter |
|---|---|
| Site ID | Your site ID, from the site's general settings or the URL of the site dashboard |
| API token | The site API token you created |
| Content types | Collection IDs, comma separated |
| Translatable fields | Field slugs, comma separated |
| Publish these locales | The target locales to write back |
Select Connect, then Test connection. A successful test names the site.
What gets imported
For every item in each collection, transglot reads the primary-locale variant and imports the mapped fields that hold text. When an item has a name field, its value becomes the description on the item's keys.
How translations are written back
In Webflow each locale is a separate variant of the same item. transglot matches each target language to one of the site's secondary locales (by the full locale tag first, then by the language alone) and updates only that variant's mapped fields.
- A language with no matching secondary locale on the site is skipped.
- The primary (source) variant is a separate record, and Webflow refuses writes to it through this path.
- transglot updates the items but does not publish the site. Publish in Webflow when you want the translations live.
Troubleshooting
... the credentials were rejected.The token is wrong, revoked, or lacks CMS write access.... the site, collection or item was not found, check the settings.Check Site ID and the collection IDs.... the item changed underneath us (conflict), retry.Run Publish to CMS again.- Translations for one language never arrive: check that language is a secondary locale on the site and that the item has a variant for it.