Run your Webflow site translations from one review desk

Build me a localization desk that my marketing team works out of, so translating our website stops being an export to spreadsheet and reimport ritual. On first run I pick a Webflow site and a CMS collection using List Collections, and I choose the target languages I care about, mapping each one to the matching Webflow CMS locale. Use Get Collection Details to read the collection schema so the app knows every field slug and field type, and treat only plain text and rich text fields as translatable, leaving references, images, switches, and slugs alone.

The home screen is a grid of every item in the collection, loaded with List Collection Items and paged through until I have them all. Each row is one item, and there is a column per target language showing that item's status in that language as Untranslated, Drafted, Reviewed, or Live, so the gaps are obvious at a glance. Show counts per language across the top, let me filter down to just the gaps or to a single language, and let me search by item name. Use List Collection Items Live to confirm what is genuinely published on the public site.

Clicking an item opens a side by side editor for one target language. The left column shows the original English fields pulled with Get Collection Item, read only. The right column shows the translated version of each field, fully editable in place. Above the fields, let me switch between target languages without leaving the item.

Translations come from JigsawStack Translate Text. Send all of an item's translatable fields in a single call using the array form rather than one call per field. Two rules matter here. First, I keep a glossary of brand terms and product names that must be left untranslated, editable on its own settings screen. Before translating, replace every glossary occurrence with a placeholder token, then restore the original term afterward, and show me in the editor which terms were protected. Second, rich text fields must keep their formatting rather than coming back as flattened plain text. Webflow rich text is HTML, so extract the text runs from the markup, translate those runs, and reassemble them into the identical tag structure, so headings, links, bold text, and lists all survive. Render rich text as formatted text in the editor, not as raw markup.

Give me a Check spelling action that runs JigsawStack Check Spelling over my edited text and surfaces the corrections inline, so I can accept or dismiss each one and catch typos before anything ships.

Approving writes the translated fields back to Webflow as a staged draft with Update Collection Item, keyed by field slug, passing the target locale's cmsLocaleId so the translation lands in that locale instead of overwriting the English. Approving sets that item's status for that language to Reviewed and never touches the live site. Publishing is a separate, explicit action that pushes the reviewed version live with Update Collection Item Live and sets the status to Live. Keep those two as distinct buttons, with a confirmation step on publish, because nothing should reach the public site without a human approving it first.

Add a "Translate this whole collection" button that kicks off a background agent. The agent walks every item that is still Untranslated for the selected language, fetches each one with Get Collection Item, applies the glossary masking, translates each translatable field with Translate Text, runs Check Spelling over the result, and saves each one as a staged draft with Update Collection Item against the target locale, marking it Drafted. The agent must never publish anything. When it finishes, it posts a summary to Slack with Send a Message covering how many items it queued for review, how many it skipped or failed and why, and a link back into the app so someone can start reviewing.

Webflow does not track review state, so the app stores per item and per language status itself, along with the glossary, the locale mapping, and the timestamp of the last translation. That status has to persist across sessions and be shared by everyone on the team, so two people never end up reviewing the same item twice.