Headless CMS with visual editor for content management and delivery across multiple platforms
Headless CMS with visual editor for content management and delivery across multiple platforms On Nagent, Storyblok is exposed as a fully-configurable developer tools integration that any agent can call — 10 actions, and API_KEY, OAUTH2 authentication. No code is required to wire Storyblok into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Storyblok 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 Storyblok 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 Storyblok, with input parameters and output schema. Drop these into any step of an agent built in Helix.
STORYBLOK_FETCH_CONTENT_TYPE_ITEMS_GRAPHQLFetch multiple stories/content items using Storyblok's GraphQL API with filtering and pagination. Use starts_with with language code prefix (e.g., 'es/*', 'hi/*') to retrieve translated content in specific languages.
Input parameters
Page number for pagination (multiplied by per_page). Default: 1.
Number of items per page. Default: 25, Maximum: 100.
Filter by specific tag slugs (comma-separated, acts as OR operator).
Filter by full_slug path to retrieve entries from a specific folder or language. Use language code prefix (e.g., 'es/*', 'hi/*', 'en/*') to retrieve translated content, or folder paths (e.g., 'articles/', 'blog/').
The content type name to query (e.g., 'Page', 'Article', 'Product'). Storyblok generates a GraphQL query field by appending 'Items' to this name (e.g., 'Page' becomes 'PageItems').
Comma-separated list of slugs to exclude from results.
Filter stories published before a specific date (ISO 8601 format).
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
STORYBLOK_FETCH_GRAPHQL_CONTENT_ITEMTool to fetch a single story in a specific language using Storyblok GraphQL API with field-level translations. For each content type (e.g., Page), Storyblok generates a ContentTypeItem field (e.g., PageItem). Use when you need to retrieve a specific story by ID or slug with optional language translation.
Input parameters
Slug, ID, or UUID of the story to fetch. For field-level translations, prepend language code to the ID (e.g., 'es/home' for Spanish version of 'home'). Otherwise, use the story slug, numeric ID, or UUID.
Language code for field-level translations (e.g., 'en', 'es', 'hi'). When provided, queries the translated content. For field-level translations, you can either use this parameter or prepend the language code to the ID.
The content type name to query (e.g., 'Page', 'Article', 'Product'). Storyblok generates a '<ContentType>Item' field for each content type (e.g., 'PageItem' for 'Page'). This will be automatically formatted to '<ContentType>Item' in the GraphQL query.
Resolve related content using dot-notation format (e.g., 'article.categories' to resolve the 'categories' field in 'article' component). Multiple relations can be comma-separated.
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
STORYBLOK_GET_APPTool to retrieve a Storyblok extension/app by ID using the Management API. Use when you need to fetch details about a specific extension or app installed in Storyblok.
Input parameters
The numeric identifier for the extension/app to retrieve.
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
STORYBLOK_GET_DATASOURCE_ENTRIESTool to retrieve datasource entries from Storyblok via GraphQL API. Use when you need to fetch datasource data. Returns datasource entries with fields like id, name, value, and dimension_value.
Input parameters
The GraphQL query string to retrieve datasource entries. Use 'DatasourceEntries' query with fields like id, name, value, dimension_value. Example: '{ DatasourceEntries { items { id name value } } }'
Content version to retrieve. Use 'draft' for draft content or 'published' for published content.
Optional variables for the GraphQL query. Use when your query contains variable placeholders.
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
STORYBLOK_GET_GRAPHQL_RATE_LIMITTool to retrieve rate limit information from Storyblok GraphQL API. Use when you need to check the maximum cost per request to calculate safe request rates (100 / maxCost = requests per second).
Input parameters
GraphQL query string to get rate limit information. Use the default value to query the maxCost field, which represents the approximation of the maximum cost of a single request.
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
STORYBLOK_GET_PAGE_ITEMTool to retrieve a single page item by ID or slug from Storyblok using GraphQL. Use when you need to fetch specific page content with custom field selection. Supports both draft and published versions.
Input parameters
The ID or slug of the page item to retrieve. Use either numeric ID or string slug like 'home'.
GraphQL fields to retrieve from the PageItem. Customize to fetch only needed fields.
Version of the content to retrieve - either 'draft' or 'published'.
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
STORYBLOK_LIST_GRAPHQL_CONTENT_TYPE_ITEMSTool to retrieve multiple content items with pagination, filtering, and relation resolution for any Storyblok content type via GraphQL. Content types are dynamically generated as \[ContentType\]Items (e.g., PageItems, BlogArticleItems). Use when you need to query structured content with flexible field selection and filtering.
Input parameters
GraphQL query string for retrieving content items. Use the pattern: { \[ContentType\]Items { total items { id name slug full_slug created_at published_at uuid content } } } where \[ContentType\] is dynamically generated (e.g., PageItems, BlogArticleItems). Available fields: id, name, slug, full_slug, parent_id, position, is_startpage, first_published_at, created_at, published_at, uuid, content, alternates, translated_slugs. Supports pagination (page, per_page), filtering (with_tag, starts_with, by_uuids, excluding_ids), and language parameter for localized content.
Content version to retrieve. Use 'published' for published content (default) or 'draft' for unpublished/draft 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
STORYBLOK_QUERY_PAGE_ITEMSExecute GraphQL queries to retrieve multiple page items from Storyblok with filtering options. Use when you need to fetch page content with filters like path prefix, publish date, or slug exclusions.
Input parameters
GraphQL query string for PageItems. PageItems is a dynamically generated query type for the 'page' content type that retrieves multiple page items. Include fields like id, name, slug, full_slug, uuid, content, published_at, etc.
Optional variables for the GraphQL query. Can include filters like starts_with (filter by path), first_published_at_lt (filter by publish date), excluding_slugs (exclude specific slugs), or pagination parameters like first, after, last, before.
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
STORYBLOK_RETRIEVE_LINKS_GRAPHQLTool to retrieve links for navigation using Storyblok's GraphQL API. Use when you need to fetch navigation links with their metadata (id, uuid, slug, name, published status).
Input parameters
GraphQL query string to retrieve links. Default query fetches all standard link fields (id, uuid, slug, name, published).
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
STORYBLOK_RETRIEVE_TAGSTool to retrieve tags from Storyblok via GraphQL API. Use when you need to fetch available tags for content organization and filtering.
Input parameters
GraphQL query to retrieve tags. Use the default query to fetch all tag names, or customize to fetch additional tag fields.
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 53 agents privately built on Nagent that already use Storyblok.
Build on Nagent
Connect Storyblok 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 Storyblok, and click "Connect Now." You'll authenticate with API_KEY, OAUTH2 — Nagent handles credential storage and refresh automatically. Once connected, Storyblok is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Storyblok is connected, you configure its 10 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Storyblok 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 Storyblok event fires, the agent kicks off automatically.
Every Storyblok 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 Storyblok ships with 10 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Storyblok together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Storyblok-based workflows tailored to your business.