NagentArtefacts
Dev & Technology
Enterprise and White Glove
Company
Prismic connects to a Nagent workspace with an API key. Once it is connected, agents can call 5 Prismic actions, such as "Get Prismic Documents with Fulltext Search", "Get Prismic Repository Info" and "Get Prismic Tags". Nothing is enabled on connect: each action is allowed one at a time, and an action with side effects runs or waits for a person according to the agent's level.
Every operation an agent can call against Prismic, with input parameters and output schema.
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
Agents can call 5 Prismic actions on Nagent, including "Get Prismic Documents with Fulltext Search", "Get Prismic Repository Info" and "Get Prismic Tags". Get Prismic Documents with Fulltext Search: Search Prismic documents using full-text search. Each action is listed on this page with its input parameters and its output.
Prismic connects with an API key, under your workspace's own connection. Nothing is enabled on connect: each action is allowed one at a time and can be scoped to the agents that need it.
Get Prismic Documents with Fulltext Search takes 1 required input: q. It also takes 6 optional inputs: lang, page, fetch, pageSize, orderings and fetchLinks. It returns data, error and successful.