Connect your app to Contentful

Contentful is a headless CMS that separates content management from how content is presented. The Contentful connector lets your Lovable app fetch published content from your Contentful space through the Content Delivery API. It’s designed for content-driven pages, product catalogs, blogs, and documentation where editors work in Contentful and your app renders the result. Contentful is available as an app + chat connector: one shared connection that works in the chat while you build and in your published apps. With Contentful, your app can:

• Fetch published entries, assets, and content types from your space
• Filter and paginate entries by content type, locale, or field values
• Resolve linked entries and assets so pages render complete content
• Render rich text fields in your app

The Contentful connector is read-only and targets the Content Delivery API. It’s a good fit when your content is authored in Contentful and your Lovable app is the front end that renders it.

​

Common use cases and example apps

These examples show what you can build with Contentful, each with a prompt to start from.

​

How to connect Contentful

Who can create Contentful connections depends on your plan and workspace settings. App + chat connectors are available by default on Free, Pro, and Business plans. On Enterprise plans, they are effectively disabled at first: Who can create connections and clients defaults to No one until an admin changes it in Connectors → Admin settings → App + chat connectors. You can create multiple Contentful connections using different spaces or access tokens, which is useful for separating environments (for example, development and production) or connecting several Contentful spaces. When the connection is created, you can link it to the projects where you want to use it. Anyone building in a project can ask Lovable in chat to link their project to it.

​

Prerequisites

Before connecting Contentful, make sure you have:

• A Contentful account with a space that contains published content
• The Space ID of that space
• A Content Delivery API access token for that space
• Permission to create connections in your Lovable workspace (see Who can create connections and clients)

​

Step 1: Find your Space ID and create an access token

A Content Delivery API access token lets your Lovable app read published content from one Contentful space. Both values you need are in the Contentful web app. To find your Space ID and create a token: See Contentful documentation for more: Find your space ID and Authentication.

​

Step 2: Connect Contentful to Lovable

You can create multiple connections using different spaces or access tokens. When connected, anyone building in a project can ask Lovable in chat to link their project to Contentful (based on configured connection-level access). Your Lovable apps can then fetch content from your Contentful space.

​

Working with environments

Each connection reads from one space, and Lovable makes the Space ID available to linked projects so you do not repeat it in prompts. Requests use your space’s master environment unless you ask for another one. To read from a different Contentful environment, name it when prompting Lovable, for example “load the homepage from the staging environment”.

​

Limitations

The Contentful connector is read-only and targets the Content Delivery API. The Contentful connector cannot:

• Create, update, or delete content. Editors continue to manage content in the Contentful web app.
• Fetch draft or unpublished content. The connector reaches the Content Delivery API only, not the Content Preview API.
• Call the Content Management API for content authoring, space configuration, or asset uploads.
• Receive Contentful webhooks or publish events.
• Support per-end-user Contentful login. Each connection represents a single space and access token shared across all projects linked to it.

​

Manage your connection

Connections are managed from Connectors: select , then open the connection.

• Unlink projects to remove access from specific projects while keeping the connection available for others. See Unlink projects from a connection for the steps.
• Delete the connection to remove it from the workspace entirely. Deleting is permanent. It removes the credentials from all linked projects, and app features that use stop working until a new connection is added. See Delete a connection for the steps and who can delete.