The Contentful GraphQL Content API allows developers to query and deliver content using GraphQL, providing a flexible and efficient way to access content stored in Contentful.
The Contentful GraphQL Content API allows developers to query and deliver content using GraphQL, providing a flexible and efficient way to access content stored in Contentful. On Nagent, Contentful Graphql is exposed as a fully-configurable developer tools integration that any agent can call — 2 actions, and API key authentication. No code is required to wire Contentful Graphql into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Contentful Graphql to automate the kinds of tasks developer tools 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 Contentful Graphql 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 Contentful Graphql, with input parameters and output schema. Drop these into any step of an agent built in Helix.
CONTENTFUL_GRAPHQL_GET_CMA_TOKENTool to retrieve a Contentful Management API (CMA) access token. Use when making CMA calls to ensure valid authorization.
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
CONTENTFUL_GRAPHQL_GRAPH_QL_CONTENT_API_PERSISTED_QUERYExecute a GraphQL query using Automatic Persisted Queries (APQ). APQ reduces bandwidth by sending only a SHA256 hash instead of the full query text after initial registration. Workflow: 1. First request: Include both sha256_hash and query text to register the query 2. Subsequent requests: Send only sha256_hash and variables - the server uses the cached query Common errors: - PersistedQueryNotFound: Query not cached; include the full query text - PersistedQueryMismatch: Hash doesn't match query text; recompute the hash - UNKNOWN_SPACE: Invalid space_id or access_token for the space
Input parameters
Full GraphQL query text. Include on first request to register the query; omit on subsequent requests to use cached version by hash only.
APQ protocol version. Must be 1.
Contentful Space ID. Example: 'cfexampleapi' for the public demo space.
Variables for parameterized GraphQL queries. Example: {"limit": 10}
SHA256 hash of the exact GraphQL query text (64 hex characters). Compute with: echo -n 'query text' \\ | sha256sum. Uppercase is auto-converted to lowercase.
Content Delivery API (CDA) access token. Overrides the token in metadata if provided.
Contentful Environment ID. Use 'master' for the default 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 84 agents privately built on Nagent that already use Contentful Graphql.
Build on Nagent
Connect Contentful Graphql 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 Contentful Graphql, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Contentful Graphql is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Contentful Graphql is connected, you configure its 2 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Contentful Graphql 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 Contentful Graphql event fires, the agent kicks off automatically.
Every Contentful Graphql 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 Contentful Graphql ships with 2 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Contentful Graphql together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Contentful Graphql-based workflows tailored to your business.