wxrks Sync sends your Webflow site's Collection items, Pages, and Components to wxrks for translation, then writes the finished translations back into Webflow's real locale variants for each language you've enabled.

Getting from install to your first translated page only takes three steps — everything else on the Dashboard is either automatic or optional.

Click Sign in with Webflow and authorize the app on the Webflow site you want to translate. That's it — there's nothing else to configure on the Webflow side. This app automatically detects your site's primary language and every secondary locale you've already enabled in Webflow's own Localization settings.

In the app, go to Settings → wxrks connection → Keys and enter your wxrks access key and secret. These are validated against wxrks the moment you click Save & test connection, so a typo is caught immediately instead of failing on your first real send.

Every automation and one-time send under this account uses these credentials — without them, translation features are unavailable.

This is the step that actually gets translated content flowing back into Webflow — without it, wxrks has no way to tell this app a translation is ready.

Once those 3 steps are done, the app's Dashboard tracks a few more checks — none of them block you from sending content, they're just visibility:

The Dashboard's setup checklist collapses itself automatically once everything required is done, and shows an all-time summary (words translated, runs sent, active languages, active automations) front and center instead.

Settings is split into tabs down the left. This article covers the three that establish who you're syncing as: General, wxrks connection, and LLM connectors.

An optional Anthropic API key. Today it's used for exactly one thing: as a fallback for Slug handling's "Transliterate" mode, for scripts the built-in transliteration table can't handle on its own (Korean, Japanese, Chinese, Arabic, Hebrew, etc.) — Latin, Cyrillic, and Greek are always handled locally without it.

Two settings tabs decide exactly what gets translated, and how translated URLs are built: Slug handling and Field exclusions.

Every translated CMS item, page, or component keeps its own slug in each target locale. This setting controls what that translated slug looks like:

Webflow requires slugs to be dashes (not underscores), lowercase, and URL-safe — this app enforces that automatically no matter which mode is selected.

A new slug is applied automatically the moment translation completes — there's no manual review or approval step to hold it for.

By default, this app auto-selects every text-type field across every collection as translatable. Expand any collection in Settings → Field exclusions to turn off specific fields that shouldn't be sent for translation — typical candidates are internal notes, IDs, or any field already handled by Slug handling above.

This is where a send starts — either everything on your site, or a hand-picked subset, walked through a 3-step wizard before anything actually goes to wxrks.

Item and word counts load progressively per collection — on a large site this can take a moment, shown as “N of M collections done” while it works in the background.

When you choose Select specific content and open a collection, page folder, or the components list, each item shows a Status pill — not just whether it was ever sent, but whether it's actually up to date right now:

Status always looks at the most recent delivery attempt — republishing a page or CMS item after it's already been translated automatically flips it back to Stale.

Both scopes send through the exact same wizard. A good rule of thumb: start with All content unless you have a specific reason to hold something back from translation.

Target languages (pulled from Webflow's own Localization settings), the translation workflow (starts at Automatic Translation, with optional review steps after), and — under Advanced — the wxrks org unit and project name.

One-time send (right now), or a recurring pull content automation that checks for matching new/changed content on a schedule.

A last look at content scope, run type, and translation settings — nothing is sent until this step's button is clicked.

If a workflow has more than one step, Webflow is only updated once the last step delivers — an intermediate step finishing never partially overwrites your site.

Everything that's scheduled, queued, or already happened lives on the Runs page, organized into three tabs: History, Recurring Automation, and Pending Queue.

Every past run, one-time or automation-triggered, with delivery status per item and any errors encountered along the way. Filter by All, One-time, or Recurring.

Every automation created from the Send to wxrks wizard's “Recurring pull content automation” option is listed here, with controls to pause, resume, or archive it. Archived automations are hidden by default — a Show archived link appears whenever any exist.

New and edited Webflow content appears here in real time, as Webflow's CMS webhook delivers item-changed events — then runs under whichever automation matches it, on that automation's own schedule.