Kontent.ai is a headless CMS that delivers content via API, allowing developers to build websites and applications using their preferred frameworks, languages, or libraries.
Kontent.ai is a headless CMS that delivers content via API, allowing developers to build websites and applications using their preferred frameworks, languages, or libraries. On Nagent, Kontent.ai is exposed as a fully-configurable documents integration that any agent can call — 7 actions, and API key authentication. No code is required to wire Kontent.ai into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Kontent.ai to automate the kinds of tasks documents teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Kontent.ai into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Kontent.ai, with input parameters and output schema. Drop these into any step of an agent built in Helix.
KONTENT_AI_GET_CONTENT_ITEMTool to retrieve a specific content item by its identifier. Use after confirming the environment ID and item identifier.
Input parameters
Optional environment/project ID. Defaults to the connected environment.
Identifier of the content item. Use internal ID, or prefix with 'external-id/' or 'codename/' for external IDs or codenames respectively.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KONTENT_AI_GET_LANGUAGETool to retrieve a specific language by its ID. Supports Management API directly and Delivery API via normalization.
Input parameters
Optional environment/project ID. Defaults to the connected environment.
Identifier of the language. Use internal ID (UUID), or prefix with 'external-id/' for external ID, or 'codename/' for language codename.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KONTENT_AI_GET_LANGUAGE_VARIANTTool to retrieve a specific language variant of a content item. Use after confirming the item and language identifiers when needing localized content.
Input parameters
Optional environment/project ID. Defaults to the connected environment.
Identifier of the language variant. Use internal ID, or prefix with 'codename/' for codename of the language.
Identifier of the content item. Use internal ID, or prefix with 'external-id/' or 'codename/' for external IDs or codenames respectively.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KONTENT_AI_GET_TYPES_ELEMENTTool to retrieve a specific element from a content type by codename. Use when you need to get details about an element's configuration within a content type.
Input parameters
Codename of the content type containing the element.
Optional environment/project ID. Defaults to the connected environment.
Codename of the element within the content type.
Optional flag to determine whether the API waits while fetching latest content. Set to true to wait for new content to be loaded.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KONTENT_AI_LIST_CONTENT_ITEMSTool to list content items from the Delivery API. Use when fetching content items for a specified environment, optionally providing a continuation token for pagination.
Input parameters
Optional environment/project ID. Defaults to the connected environment.
Continuation token to fetch the next page of results
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KONTENT_AI_LIST_CONTENT_TYPESTool to list content types within a Kontent.ai environment. Use when you need to retrieve a paginated list of content type definitions. Use after confirming the environment ID.
Input parameters
Continuation token from a previous response to fetch the next page.
Optional environment/project ID. Defaults to the connected environment.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KONTENT_AI_LIST_LANGUAGESTool to list languages in a Kontent.ai project. Use when you need to retrieve all languages for a specified environment after confirming the project ID.
Input parameters
Number of items to skip for pagination
Maximum number of items to return
Specifies the ordering of languages, e.g., codename\[asc\]
Optional environment/project ID. Defaults to the connected environment.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 66 agents privately built on Nagent that already use Kontent.ai.
Build on Nagent
Connect Kontent.ai to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Kontent.ai, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Kontent.ai is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Kontent.ai is connected, you configure its 7 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Kontent.ai steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Kontent.ai event fires, the agent kicks off automatically.
Every Kontent.ai action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Kontent.ai ships with 7 pre-built documents actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Kontent.ai together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Kontent.ai-based workflows tailored to your business.