globalize.now now connects to Contentful: link a space, and your entries are translated when you publish them, with the translations written back into the space's own locales. globalize.now is AI-powered localization infrastructure, and until November 2026 it read from one kind of source, a Git repository. Contentful is the first source that is not a repository.

Our position is simple. Content should be translated where it lives. If your marketing pages, help articles and product copy sit in Contentful, exporting them to a separate tool and syncing them back gives you a second copy to keep in step. The connector removes that round trip. Below is what it does, how to set it up and where it stops.

What does the Contentful connector do?

It lets a Workflow watch one Contentful environment and keep its locales translated. A Workflow is the unit that does the work in globalize.now: it has an input, a list of target languages, steps that run in order, and an output.

Part of the WorkflowWith a repositoryWith Contentful
InputA GitHub repository and its watched branchesA space and a watched environment
What is readLocale filesEntries of the content types you select
Source languageThe one you pickThe environment's default locale
StepsTranslate, then QATranslate, then QA
OutputA pull requestWrite-back into the entry's locales

The steps are the same ones that translate a codebase. Only the two ends change. If you have used globalize.now on a repository, or driven it from Claude through the connector in Claude's directory, the middle of the pipeline is already familiar.

How do you connect a Contentful space?

There are six steps, and most of them happen in the Workflow builder.

  1. Start a Workflow. In the globalize.now app, open Workflows, click New workflow and choose Contentful space as the input.
  2. Install the Globalize App. The builder links straight to the install screen in Contentful. Install the app in your space, then choose Connect to Globalize in the app's configuration and approve the connection.
  3. Pick the space and environment. Each run reads from, and writes back to, the environment that name points to when the run starts.
  4. Choose content types. Keep all content types, including ones you add later, or narrow the list to the ones that should be translated.
  5. Check the languages. Target languages are filled in from the environment's locales, so there is no second language list to maintain.
  6. Publish the Workflow. The next entry you publish in Contentful is translated.

New to globalize.now? The get-started guide covers the account, and the pricing page has the plans. The connector is available to every organisation.

What starts a translation?

Four things can, and you choose which of the automatic ones are switched on.

  • An entry is published. The entry is translated and published again with its translations.
  • A draft is edited. A run starts five minutes after the last edit. The translations land as drafts, so an editor can read them before anyone publishes.
  • An editor asks for it. The Globalize sidebar in the Contentful entry editor translates that one entry and shows the status of the run.
  • A manual run. Started in globalize.now, it translates every entry the Workflow selects. This is how you backfill a space on day one.

The draft trigger is the one to think about. Switch it on if translators or market owners read content before it goes live. Leave it off if published is the only state that matters to you.

Which fields are translated?

Plain text fields, Rich Text and Markdown. That covers titles, summaries, body copy, button labels and the long-form fields most content models are built from. Other field types are left as they are.

One rule comes from Contentful itself: a field is translated only if localization is switched on for it. Contentful localizes per field, and you enable localization on each field in the content model. A field without it holds one value for the default locale and has nowhere to store a German or Japanese version.

What does your Contentful space need first?

Two things: a locale for every target language, and localized fields.

Locales in Contentful belong to the environment, and every environment has one default locale. The Workflow always translates from that default locale. If you ask for a language the environment has no locale for, the run still translates it and keeps the result in globalize.now, and the run page names it as not delivered. Add the locale in Contentful and the next run writes it back.

If a run fails because it found no source text, check these two things before anything else. The usual cause is a field that is not localized or an environment with only its default locale.

What happens to translations you already have?

They are adopted, not replaced. The first time a run sees a translation in Contentful that globalize.now did not write, it takes it over as it stands. It is not translated again and it uses no translation credit. Edits made in Contentful afterwards are kept in the same way.

This matters if you are moving in with years of translated entries. Connecting the space does not put that work at risk, and the first run does not bill you for it.

How is quality kept consistent?

Every language passes a QA step before anything is written back. QA runs five checks and an AI review. Style guides and context are Assets in your organisation that you attach to the Workflow, so tone and form of address are set once and applied on every run.

The run page then shows delivery entry by entry, including anything that was not written.

What does the connector not do?

It does not replace Contentful. Your content model, your delivery API, your previews and your publishing rights stay where they are. globalize.now reads entries and writes locales, nothing more.

It does not translate fields that are not text, and it does not create locales for you. Adding a market is still a decision you make in Contentful.

It also does not touch your code. If your app's interface strings are hardcoded in components, that is a separate, one-time conversion that runs when you connect a repository. The developers page and the MCP server guide cover that side.

Who is this for?

Teams whose product strings are in Git and whose content is in a CMS. Until now that meant two translation setups, or one setup and a lot of copying. With a repository Workflow and a Contentful Workflow in the same organisation, both halves run through the same translate and QA steps.

It also fits content teams with no repository in the picture at all: a marketing site, a help centre or a knowledge base modelled in Contentful and published in several languages.

Where to start

Open app.globalize.now, create a Workflow with a Contentful input and publish one entry. Then read the German or Spanish locale of that entry in Contentful. If you would rather read the full reference first, the help centre article has every setting.

globalize.now turns hardcoded app copy into translation-ready locale files and keeps them updated as you ship.

Try globalize.now free