Let your team write in Contentful while the live site renders only published content from its own database.
Describe the result in chat. The agent installs the integration, wires the app, and checks the connection before you ship.
What the agent sets up
One request covers the app code, provider connection, and working proof.
Creates a dedicated read-only delivery key, so the live site can never show an unpublished draft.
Syncs published entries and assets into the app database, so pages render from local data with nothing fetched at request time.
Registers the publish webhook at deploy so a new entry goes live within seconds of publishing.
Values stay out of the conversation
Private values stay server-side. Stored values are resolved only by server tools. The agent receives the field name, runtime, verification status, and fix-it link, never the stored value.
Content Management API personal access token with manage scope and permission to create webhooks and Delivery API keys.
Create or manage this keyA blocker comes with the next move
Contrast probes https://api.contentful.com from the server. It classifies a missing key, invalid key or permission, and an unreachable provider separately instead of returning a generic failure.
Each blocked result explains what failed and links to the provider screen where you can fix it. Run verification again and the project moves to Verified only after the provider accepts the probe.
Publish in Contentful, live in seconds
Writers work in Contentful; the site reads through a delivery key that cannot see drafts. Publishing an entry updates the deployed site without a rebuild or a cache purge.