Inverb
Back to docs

Setup

Connect Contentful

Attach a Contentful space, sync schema, and scope what content should show up in Inverb.

2 min readUpdated May 15, 2026

Use Settings > Contentful to connect the project to a Contentful space.

Connection fields

The current setup expects:

  • Space ID
  • Environment ID
  • Preview token
  • Management token

Once those are saved, you can refresh schema and start working with synced content.

Refresh schema

After connecting, run schema refresh so Inverb can inspect the content model it should work against.

Do this again when:

  • new content types are added
  • fields change
  • locale configuration changes in Contentful

Top-level content types

Use the top-level content type selection to decide what should appear in the Content listing.

This is a practical scoping tool. It helps keep the main queue focused on the entry types your team actually localizes.

Top-level content types also affect tag-based workflows. Inverb only resolves Contentful tag filters and tag-based batches against the top-level content types selected for the project.

Page links

Use Page Links when reviewers need to open the live or preview page for a Contentful entry directly from Inverb.

Page links are built from three parts:

  • Environments: the site hosts you want to link to, such as production or preview.
  • Locale path overrides: optional path segments used when target locales do not match your public URL structure.
  • URL patterns: per-content-type path templates that turn entry fields into page URLs.

The preferred pattern is:

{locale.path_prefix}/blog/{entry.fields.slug}/

Available placeholders include:

  • {entry.fields.slug} for an entry field value
  • {entry.id} for the Contentful entry ID
  • {locale.path_prefix} for the locale-aware path segment

The source locale does not receive a locale prefix. Target locales use their lowercase Contentful locale code unless you configure an override.

Publishing mode

The Contentful settings also include publishing mode.

  • all_locales: standard publish behavior for the entry
  • locale_based: intended for locale-scoped publishing flows

Choose the mode that matches how your Contentful environment handles publish actions. If your team relies on locale-specific publishing behavior, validate that end to end before turning on automation.

Good first check

After setup:

  1. Open the Content screen.
  2. Confirm expected entries appear.
  3. Open one entry and verify the source locale content is what you expect.