Prismic is a headless CMS that enables developers and content teams to manage and deliver content seamlessly across various platforms.
Prismic is a headless CMS that enables developers and content teams to manage and deliver content seamlessly across various platforms. On Nagent, Prismic is exposed as a fully-configurable website builders integration that any agent can call — 5 actions, and API key authentication. No code is required to wire Prismic into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Prismic to automate the kinds of tasks website builders 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 Prismic 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 Prismic, with input parameters and output schema. Drop these into any step of an agent built in Helix.
PRISMIC_CONTENT_API_GET_DOCUMENTS_WITH_FULLTEXT_SEARCHSearch Prismic documents using full-text search. Searches across all text fields in documents for the specified terms. The search is case-insensitive and matches based on root words. Automatically retrieves the current master ref. Returns paginated results ordered by relevance.
Input parameters
Full-text search query in Prismic predicate format. Must be wrapped in double square brackets. Format: \[\[fulltext(document, "your search terms")\]\]. Searches across all text fields in documents. Multiple words will match documents containing all terms.
Language code (e.g., 'en-us').
Page number, must be >= 1
Comma-separated list of field API IDs to fetch.
Number of documents per page (1-100).
Sorting order, e.g., '\[my.article.date desc\]'
Comma-separated list of linked document fields to fetch.
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
PRISMIC_CONTENT_API_QUERY_DOCUMENTSTool to query Prismic documents using predicates and pagination. Use when you need to fetch multiple documents from a repository after obtaining a ref.
Input parameters
Query predicate(s) to filter documents using Prismic predicate syntax. Use double brackets for predicates: '\[\[at(document.type, "page")\]\]'. For multiple predicates, combine them in one string: '\[\[at(document.type, "blog")\]\[at(document.tags, \["featured"\])\]\]'.
Content release reference ID from the repository (typically the master ref). Use PRISMIC_REPOSITORY_API_GET_REFS action to obtain valid ref values.
Language code to query (e.g., 'en-us'), default '*' for all languages
Page number for pagination, starting from 1
Document ID to paginate after for deep pagination.
Comma-separated list of specific fields to fetch for each document (e.g., 'document.title,document.description'). Reduces response size by only including specified fields.
Number of documents per page (1-100)
Sort order, e.g., '\[my.article.date desc\]'
Comma-separated list of fields from linked documents to include in the response (e.g., 'author.name,category.title'). Allows fetching related content in a single query.
GraphQuery to specify which fields to return.
Private API content token for authentication, if required.
Reference of integration fields content.
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
PRISMIC_REPOSITORY_API_GET_INFORetrieves comprehensive metadata about a Prismic repository including available refs (content versions), custom types, languages, tags, bookmarks, and API forms. This is typically the first API call made after authentication to discover repository configuration and available content endpoints. The 'refs' field is particularly important as refs are required for querying documents via the Content API.
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
PRISMIC_TAGS_API_GET_ALL_TAGSTool to retrieve all tags from Prismic repository. Use when you need the full list of tags for filtering or categorization.
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
PRISMIC_TYPES_API_GET_TYPESRetrieves all custom types (content models) defined in the Prismic repository. Custom types define the structure of content in Prismic. This action returns metadata about each custom type including its ID, label, structure definition (JSON schema), and whether it's repeatable. Use this to discover available content types before querying documents, or to understand the content model of a repository. Returns an empty list if no custom types are defined in the repository.
Input parameters
Page number for pagination (1-indexed). Use with limit parameter to navigate through results.
Sort order for results. Common values include 'name' to sort alphabetically by custom type name.
Maximum number of custom types to return per page. If not specified, returns all custom types.
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 75 agents privately built on Nagent that already use Prismic.
Build on Nagent
Connect Prismic 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 Prismic, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Prismic is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Prismic is connected, you configure its 5 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Prismic 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 Prismic event fires, the agent kicks off automatically.
Every Prismic 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 Prismic ships with 5 pre-built website builders actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Prismic together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Prismic-based workflows tailored to your business.