Integrations

Pulls from your CMS. Pushes back into the locale fields.

No copy-paste, no exported spreadsheets. Verb Atlas reads your source content where it lives and writes approved translations back into the right locale field.

Six ways to connect

Your source

Pages · products · strings

Verb Atlas

Glossary · memory · review

Locale fields

Approved · mapped · ready

Read
Translate
Write back

Connection 01

Sanity

Locale field mapping on document schemas, sync on publish, conflict handling per field.

Connected workflow
sanity.connector
Field mappingMap internationalized fields or locale-suffixed fields per document type
Sync triggerOn publish, on schedule, or manual from the dashboard
ConflictsDivergent edits surface for a human decision; nothing is overwritten silently
SourceVerb AtlasSanity

Connection 02

Webflow

Reads localized collections and static page content, writes approved copy back into the matching locale.

Connected workflow
webflow.connector
Field mappingCMS collections and page-level static text
Sync triggerOn publish or scheduled
ConflictsLocale-side edits flagged before overwrite
SourceVerb AtlasWebflow

Connection 03

WordPress

Works with common multilingual plugins as well as separate language sites.

Connected workflow
wordpress.connector
Field mappingPosts, pages, custom fields, taxonomies
Sync triggerOn save, on publish or scheduled
ConflictsRevision kept for every write
SourceVerb AtlasWordPress

Connection 04

Shopify

Built for catalogues: product titles, descriptions, options and metafields at SKU volume.

Connected workflow
shopify.connector
Field mappingProducts, collections, metafields, theme strings
Sync triggerBulk run or incremental on change
ConflictsLocked glossary enforced on every product title
SourceVerb AtlasShopify

Connection 05

String files

JSON, YAML, XLIFF and CSV for app and product localization, keys and placeholders preserved.

Connected workflow
strings.connector
Field mappingKey-based, nested structures supported
Sync triggerUpload, or connect a repository branch
ConflictsDiff-only syncs on release
SourceVerb AtlasString files

Connection 06

API and custom

A REST API for anything not on the list, with the same glossary, memory and review rules applied.

Connected workflow
api.connector
Field mappingYou define the payload shape
Sync triggerYour call
ConflictsApproval state returned with every segment
SourceVerb AtlasAPI and custom

Honest limits

What isn't supported yet

Contentful and Strapi

On the roadmap. The API works today if you need them now.

In-context visual editing

You review in Verb Atlas, not inside your site preview.

Live machine fallback

We will not publish unapproved output, by design.

Connect your stack in an afternoon

Tell us what you publish on and we will map the locale fields with you on the demo call.