--- title: "Contentful Integration" description: "Connect AI agents to Contentful, the API-first headless CMS. Agents create, update, publish, archive, and delete entries and assets, manage content types and locales, and read published content through the cached Delivery API." url: https://flowrunner.ai/integrations/contentful date_modified: 2026-08-07T17:20:23-07:00 --- # Contentful [CMS & Content](https://flowrunner.ai/integrations/category/cms-content) Connect AI agents to Contentful, the API-first headless CMS. Agents create, update, publish, archive, and delete entries and assets, manage content types and locales, and read published content through the cached Delivery API. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 22 actions · API key · available [Contentful website](https://contentful.com/) · [Platform Documentation](https://www.contentful.com/developers/docs/references/content-management-api/) · Capability data verified 2026-08-12 1. A new content row lands in a backlog sheet or upstream system 2. Agent reads the row and maps its fields to the content type 3. Agent confirms required fields and locale values are present 4. Agent stages the entry with Create Entry as a draft 5. Agent fetches the current version so the publish call is safe 6. An editor approves the draft before it publishes to the live site ## What This Integration Enables An agent can create entries as drafts, get and list entries including unpublished changes, update fields, and publish, unpublish, archive, unarchive, or delete them through the Content Management API. It handles Contentful's optimistic locking for you: every write to an existing resource needs the current version, and the agent fetches it automatically when you leave the version blank. Field values can be passed as a simple map and are wrapped into Contentful's locale-keyed shape using the default locale. Beyond entries, the agent manages assets end to end (create, process, publish, and delete), reads published content quickly through the cached Delivery API, and manages the content model itself by listing, creating, and activating content types and listing locales. This lets an agent run a full editorial pipeline that drafts, reviews, and publishes on a schedule, while a person still owns the moment a draft becomes public. ### Without FlowRunner **Manual entry creation**: Someone retypes each backlog row into the Contentful web app by hand **Publishing has no gate**: Drafts go live whenever an editor remembers to click publish **Localization drift**: Locale values get filled in inconsistently across entries ### With FlowRunner **Entries staged automatically**: The agent drafts each backlog row as an entry with fields mapped **Publishing is a decision**: An editor signs off before the agent publishes to the Delivery API **Locales handled on entry**: The agent wraps field values into the right locale as it drafts ## Use Case Scenarios ### Draft a Content Backlog The agent reads a batch of rows from a backlog in [Google Sheets](https://flowrunner.ai/integrations/google-sheets), maps each row to a content type, and calls Create Entry to stage it as a draft with localized fields set. The team opens Contentful to a queue of review-ready drafts instead of a spreadsheet and a blank editor. ### Keep Two Systems in Sync When new content is created in another platform, the agent mirrors it into Contentful with Create Entry so both stay aligned, and logs each sync so there is an audit trail of what moved and when. Content maintained in one place stops drifting from its copy in the other. ### Publish After Review Once an editor approves a drafted entry, the agent fetches the current version, calls Publish Entry, and posts the entry ID and title to the editorial channel in [Slack](https://flowrunner.ai/integrations/slack) so the team knows it is live. The routine handles the mechanics; the editor owns the go-live call. ## Human-in-Loop Highlight Drafting, updating, and reading entries are safe to automate, so the agent handles them without interruption. Publishing is different, because a Publish Entry call pushes content to the Content Delivery API where every site and app reading Contentful will serve it immediately. So when a flow reaches the publish step, the agent stops. It routes the drafted entry to an editor as a [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) step, showing the title, the content type, the fields it set, and a preview link, and asks: "Publish this entry to the live Delivery API, or hold for edits?" On approval the agent fetches the current version and calls Publish Entry. On hold, the entry stays a draft and nothing reaches the public API. The AI does the assembly; the decision to go live gets a person. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 22 actions ### Entries 9 - **Create Entry** Creates a new entry of a given content type as a draft, with field values passed as a simple map and wrapped into the locale-keyed shape using the default locale. - **Get Entry** Retrieves a single entry, including drafts and unpublished changes, with its sys metadata and localized fields. - **List Entries** Lists entries from the Management API, including drafts, with full-text search, ordering, offset pagination, and field-level filters. - **Update Entry** Updates an entry's fields, wrapping values into the localized shape and supplying the current version automatically when you leave it blank. - **Delete Entry** Permanently deletes an entry, unpublishing it first if needed. This cannot be undone. - **Publish Entry** Publishes an entry so its current draft state is served through the Content Delivery API. - **Unpublish Entry** Removes an entry from the Delivery API while keeping the draft intact. - **Archive Entry** Hides an unpublished entry from the default list and locks it from editing until unarchived. - **Unarchive Entry** Restores an archived entry to the normal draft state so it can be edited and published again. ### Delivery 2 - **Get Published Entries** Reads published entries through the cached Delivery API, faster than the Management API, using Contentful query parameters. - **Get Published Entry** Reads a single published entry by ID through the cached Delivery API. ### Assets 6 - **Create Asset** Creates an image, document, or other file as a draft asset that must be processed and published before delivery. - **Get Asset** Retrieves a single asset by ID, including its processing state, file details, and localized metadata. - **List Assets** Lists assets from the Management API, including unprocessed and unpublished ones. - **Process Asset** Triggers processing of an asset's uploaded file for a locale, preparing it for delivery. - **Publish Asset** Publishes a processed asset so it is available through the Delivery API. - **Delete Asset** Permanently deletes an asset, unpublishing it first if needed. This cannot be undone. ### Content Types 4 - **List Content Types** Lists all content types in the configured space and environment. - **Get Content Type** Retrieves a single content type by ID, including its field definitions and display field. - **Create Content Type** Creates or updates a content type with an explicit ID and field definitions, as a draft that must be activated before use. - **Activate Content Type** Activates a content type so entries can be created against it. ### Locales 1 - **List Locales** Lists the locales configured for the space, including each code, name, default flag, and fallback settings, so you know which codes to use when localizing fields. ## Frequently Asked Questions ### What can FlowRunner do with Contentful? FlowRunner agents can run Create Entry, Get Entry, and List Entries in Contentful, plus 19 more actions. ### Does connecting Contentful to FlowRunner require OAuth? No. Contentful connects to FlowRunner with an API key, no OAuth flow required. ### Can Contentful trigger a FlowRunner workflow automatically? Contentful doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Contentful?** This integration exposes Contentful to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/contentful. Site index: https://flowrunner.ai/llms.txt