Content Operations Agent

Content Operations Agent is an AI-powered agent that automates repetitive content operations in Contentful. Describe the outcome you want in natural language, and the agent creates pages, audits content, applies metadata, and runs AI Actions across many entries at once.

Unlike AI Actions, which run a specific, pre-configured task, Content Operations Agent interprets an open-ended request, plans the steps needed to complete it, and carries out the work directly inside Contentful.

Content Operations Agent reduces the time and effort needed to complete repetitive content work at scale. Instead of managing workflows entry by entry, teams can describe a large content task in plain language and have the agent complete it faster, more consistently, and with less manual effort.

The agent works from the side panel of the web app. For single entry actions, it makes the requested update directly. For multi-entry tasks, it identifies the relevant content, proposes the changes, surfaces them for review, and applies them only after you approve.

Tip: For the best experience of the content operations it is recommended that you do the following:

1. Enable AI Actions, Content semantics and Built-in AI features in Settings → Governance → AI. 

2. Activate the Timeline mode under the Settings → Environment. 

With these features activated, this will allow the agent to access the most advanced capabilities on the platform, allowing it to solve tasks more effectively. 

Content Operations Agent is free to use through January 2027, subject to usage limits (see Usage limits) and compliant to the Fair Use Policy.

• Natural language entry: describe a new page or entry, and the agent assembles itit along with any nested or reusable references it needs. This allows for reusing existing reference entries where appropriate instead of duplicating them.

• Content audits: ask the agent to find outdated, incomplete, unlinked or missing content (for example, entries of a given content type older than a set age or missed validations) and it returns a filtered, clickable list of matching entries.

• Bulk metadata and taxonomy updates: apply tags, taxonomy concepts or other metadata across many entries in a single request.

• AI Actions integration: the agent can detect when an existing AI Action fits your request (such as a translation action) and run the action for you, including as a bulk AI Action across multiple entries.

• Releases and scheduling: the agent can add entries to a release, schedule the release for a specific date and time, and notify a Slack channel with a link to review it.

• Approval-gated changes: the agent never publishes, archives, or changes a content type without your explicit approval first.

Content Operations Agent is set up in two stages: the org admin activates the agent to spaces and environments, and a space admin then grants access to individual roles. Users will not see the agent until both stages are enabled.

Grant access of agent to spaces

1. In your organization settings, go to the AI activation tab. This page lists the agents available to your organization.

2. Select Content Operations Agent. In the Enable Content Ops Agent dialog, review the access the agent will have: read, edit, create, delete, publish, unpublish, archive, and unarchive entries, content types, and assets.
   

3. Select the spaces and environments to install the agent into, then select Install and authorize.

4. Enable the recommended features: AI Actions, Content semantics and Timelines. These features are optional, and the agent works without them, but it performs best with them enabled. Timelines must be enabled separately in each environment where you want the agent to work. Each feature links directly to its configuration screen, and its status updates live as you turn features on or off.

Access to these settings depends on your organization-level AI permissions, which are the same permissions that apply to AI Actions and Content semantics. 

Grant access to roles

Installing the agent doesn't give users access to it. Content Operations Agent and AI Actions are disabled by default for individual users, even after the space-level installation above. You grant access role by role, in each space where the agent is installed:

1. In the space settings, go to Roles & permissions. 

2. Select a role.

3. Under AI access, choose whether the role can use all agents or only specific agents.

4. Save your changes.

Repeat these steps for each role that needs access. There is no link from the installation dialog to the roles settings, so you need to open them from the space settings.

What users see

• Users whose role includes access to Content Operations Agent see the agent in the Contentful web app. To start using it, open the side panel and select the AI icon at the top right.
  [Image: ai-content-ops-agent]

• If a role doesn't include access to any agents, users with that role don't see the agent or any prompt to request access. If a role includes some agents but not others, users only see the agents they have access to.

• Let your users know when you grant them access. 

How permissions apply when the agent runs

The agent acts with the permissions of the person using it. It can only perform actions that the user's role already allows, regardless of the access listed in the installation dialog.

Content Operations Agent can detect when a task matches existing AI Action, such as translation actions, bulk runs or  that action automatically rather than generating the output itself. This keeps output consistent with any AI Actions your team has already configured and reviewed.

If you've set up specific AI Actions for common tasks, the agent will prioritize using them over improvising a response.

When a request applies to multiple entries, the agent runs AI Actions in bulk rather than running the same action one entry at a time. For example, if you ask the agent to translate several newly created entries, it identifies all the relevant entries and submits them as a single bulk run, which requires your approval before it executes.

The following limitations currently apply:

• Background/async updates: the agent does not yet post ongoing updates about what it's doing or has done outside of the active session. This is planned as an upcoming improvement.

• Not connected to Personalization: the agent cannot create personalization variants or experiments.

• No autonomous publishing: the agent will always require explicit approval before publishing, archiving, or changing a content type.

Content Operations Agent is designed for recurring content operations. Common use cases include:

Create and adapt

Use this when you need new content, such as a new landing page. Create content from a brief or adapt existing content.

• Build using existing content structures.

• Create or reuse linked content.

• Clone and adapt existing content.

This is useful for content managers for creating campaign pages, blog posts, FAQs, and market-specific versions.

Audit and update at scale

Use this when something changes across your content, such as a product detail that changes across the website. Audit, fix, apply changes in bulk, and archive.

• Update copy and metadata in bulk.

• Audit and fix missing information or broken references.

• Apply or update tags and taxonomy.

This is useful for content health checks, messaging updates, and campaign cleanup.

Prepare and release

Use this when campaign content needs to launch together. Group content and assets into a release, validate, and schedule publication.

• Group content and assets into a release.

• Validate and schedule publication.

• Notify teams through connected apps.

Also useful for product launches, regional rollouts, and website updates.

Content Operations Agent is not a general-purpose AI assistant. It's built for content operations inside Contentful and is not intended as a chat assistant for unrelated tasks.

What is the Content Operations Agent? It's a chat-based copilot inside the Contentful web app that carries out content operations for you. Allowing you to create, update, and archive entries, manage references and tags, run AI Actions, create and schedule releases. It works on the entries and content types in your space, guided by your instructions and the permissions your admin sets.

What's the difference between Content Operations Agent and AI Actions? AI Actions run a specific, pre-configured task the same way every time. The agent interprets an open-ended, natural language request, decides how to approach it (including using AI Actions where relevant), and carries out multi-step work such as creating pages, running audits, or managing releases.

What controls do space admins have? Admins must accept the AI Terms of Service before install and review the agent's full access (entries, content types and assets) on the authorization screen. Admins can add one or more policies with Allow or Deny rules, scoped to specific actions (read, create, update, publish, unpublish, delete, archive, unarchive) and optionally limited to specific content types. The agent can only do what both its configured permissions and the installing user's role allow.

Will the agent ever publish, archive, or change a content type without asking me first? No. These actions always require your explicit approval before the agent executes them.

Can the agent invent field content on its own? No. If you don't provide values for a field, the agent leaves it blank rather than generating content, unless you specifically ask it to fill the field in.

Does the agent work with Personalization? Not currently. The agent cannot create personalization variants or experiments.

Does the agent publish or change content automatically? No. Publishing always requires your explicit confirmation. The agent runs pre-publish validation first, and if any content type rule fails it reports the failure and does not publish.

How does the agent decide what to create, link, or tag? For references, it uses semantic search across your space, falling back to full-text search, and links the most relevant entry for each field. For tags and taxonomy, it matches on the content. You can reject a suggested link and the agent searches again.

Can it fill in an entry from the content I paste? Yes. Paste a draft or outline into one field and the agent completes the remaining fields from it. If an AI Action is configured for a field, the agent uses it; if not, it does a best-effort generation from your text and relevant existing content.

What happens to my data and content? Content you send to the agent is processed to carry out your request and is never used to train models. For details on how content is handled by our AI providers, see the Terms of Service.