Skip to main content
Contentful
The Contentful connector syncs entries from a Contentful space — and a specific environment — into Frontic. Each entry becomes a record on a Content feed; the connector preserves Contentful’s sys.id as the Source ID so updates land deterministically.
Auth
Access token
Update methods
Trigger · Polling
Resources
Content entries
The Contentful connector follows the standard integration model — see how integrations work for Connection, Channels, and Data Feeds. This page covers the Contentful-specific configuration.

​
Connection settings

​
string
required
Your Contentful space ID — find it in Contentful under Settings → General settings.
​
string
required
A Content Delivery API token (read-only) for your space, with access to the environments you’ll connect.

​
Channels

A Contentful channel carries which translations the connector pulls per entry.
​
string
required
A label for the channel in Frontic.
​
multiselect
required
Contentful locale codes the connector pulls per entry.
​
select
required
The translation used when an entry field is missing in another locale.

​
Data Feeds

The Contentful connector exposes one feed type: The standard Settings → Updates → Schema setup wizard applies — see Data Feeds in the overview. For Contentful specifically:

​
Per-feed config

​
string
default:"master"
Which Contentful environment this feed reads from. Defaults to master. Use this to point a feed at a sandbox/preview environment without changing the connection itself.

​
Update methods

  • Trigger — wire a Contentful webhook (Settings → Webhooks) to the feed’s inbound webhook URL to push changes in near-real-time.
  • Polling — scheduled refresh.
The connector does not expose a manual feed Refresh — use Polling or trigger a webhook from Contentful to backfill.

​
What the data looks like

​
Source ID

Each record’s Source ID is taken from Contentful’s sys.id. References between entries (sys.type === "Link") come through on the raw payload — resolve them in your Data Sync if you want denormalized fields.

​
Assets

Contentful asset entries come through alongside content entries. If you want them on a dedicated storage, configure a separate feed and filter by content type at the Data Sync layer.

​
Good to know

  • Read-only via the connector. Edits happen in Contentful. The Ingest API path is for systems that supplement Contentful with extra records, not for editing entries.
  • Reference resolution lives in the Data Sync. The connector emits entries with Link references intact; resolution into denormalized fields is your Value Composer’s job.

Storyblok

Storyblok’s connector — draft mode and folder filters.

Custom Integration

For pushing supplemental records via the Ingest API.