Storyblok

Syncs your headless content with external data sources, automates the drafting of localized pages, and monitors API rate limits to ensure site stability.

Try Storyblok in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Storyblok integration

    • Describe the outcome and Ceven picks the right Storyblok calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Storyblok data, across all 10 of its actions.
  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Storyblok access.
    • Per user and per environment credentials instead of shared keys.
  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Storyblok, when, and on whose behalf.
    • The agent pauses and asks when Storyblok is unclear instead of plowing ahead.
  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Storyblok.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Storyblok action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Storyblok, and when to use it.

Fetch content type items
Use this when you need multiple stories or content items with specific filters. Use language code prefixes for translated content.
Fetch GraphQL content item
Pull a single story in a specific language with field level translations for a specific content type.
Get extension
Retrieve details about a specific Storyblok extension or app installed in the space by its ID.
Get datasource entries
Pull datasource data including id, name, and value for global site variables.
Get GraphQL rate limit
Check the maximum cost per request to calculate safe request rates and avoid throttling.
Get page item
Retrieve a single page item by ID or slug. Supports both draft and published versions.
List GraphQL content type items
Retrieve multiple content items with pagination and relation resolution for any content type.
Query page items
Execute GraphQL queries to find pages based on path prefix, publish date, or slug exclusions.
Retrieve links
Pull navigation links with metadata like uuid, slug, and published status.
Retrieve tags
Pull available tags used for content organization and filtering.
Fetch Content Type Items (GraphQL)
Fetch 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.
Get Extension/App
Tool 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.
Query page items via GraphQL
Execute 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.
Retrieve Links via GraphQL
Tool 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).
Retrieve Tags via GraphQL
Tool to retrieve tags from Storyblok via GraphQL API. Use when you need to fetch available tags for content organization and filtering.

15 actions · scroll to see them all

Frequently asked questions

Ceven uses the Get GraphQL Rate Limit tool to monitor the cost of every request in real time. Storyblok assigns a cost to each GraphQL query based on complexity and depth. Our agent calculates the remaining budget before executing bulk operations. If a workflow is about to exceed the maximum cost per request, the agent automatically introduces a delay or splits the request into smaller batches. This prevents the 429 Too Many Requests error that often plagues large scale content migrations. You can set custom thresholds in your workflow settings to prioritize either speed or stability depending on whether you are updating a single page or thousands of items.
Yes. Ceven can interact with both the draft and published versions of your content. When using the Get Page Item or List Content Type Items tools, the agent specifies the version parameter in the API call. This allows you to build workflows that stage content in draft mode for human review before the agent triggers a publish event. For example, you can have an agent pull data from a spreadsheet, create a draft story in Storyblok, and then send a Slack notification to an editor for a final sign off before the content goes live to the public.
Ceven handles localization by utilizing the language code prefix system in GraphQL queries. When you want to fetch or update translated content, the agent uses the starts with filter combined with the specific language code, such as es for Spanish or fr for French. This ensures that the agent targets the correct localized folder within the Storyblok space. You can build a workflow that takes a primary English story and automatically generates placeholders for five other languages, then fills them as translations arrive from your external localization provider.
Yes. The agent can read and write to Storyblok datasources. Datasources are ideal for global values like phone numbers, social media handles, or site wide banners. Ceven can pull these entries to ensure consistency across different pages or update them based on external triggers. For instance, if your company changes its support email, the agent can update the single datasource entry in Storyblok, and every page referencing that datasource will reflect the change instantly without needing to edit individual pages.
Ceven primarily interacts with content items and entries rather than the structural schema of the CMS. While the agent can create and edit stories within an existing content type, it cannot define new content types or add new fields to an existing schema via the standard API tools. This is a safety measure to prevent workflows from accidentally breaking the frontend rendering logic of your website. If you need to change your content model, a developer should make those changes in the Storyblok visual editor first, after which the agent can begin managing the new fields.
Ceven uses both APIs depending on the task. The Content Delivery API is used for read operations on published content, which is highly optimized for speed and cached. The Management API is used for write operations, reading drafts, and managing extensions. When you ask the agent to fetch a live page, it uses the delivery API. When you ask it to update a story or check a draft, it switches to the management API. The agent handles the token switching and endpoint routing automatically so you only have to describe the outcome you want.
For large datasets, Ceven uses a cursor based pagination strategy through the GraphQL API. Instead of requesting all items at once, which would trigger a timeout or a rate limit error, the agent requests items in pages. It tracks the pagination token and loops through the results until the full set is retrieved. This is critical for sites with thousands of pages. You will see the agent progress through these pages in the workflow logs, ensuring that no content items are skipped during a bulk audit or update process.
Yes. Ceven can retrieve existing tags and apply new ones to content items based on specific logic. You can set up a workflow where the agent analyzes the text of a story using an LLM and then applies relevant tags in Storyblok for better organization. This is particularly useful for large blogs or knowledge bases where manual tagging is inconsistent. The agent pulls the current tag list to avoid creating duplicates and then updates the item metadata to include the new tags.

Alternatives to Storyblok

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Contentful logoContentfulStrapi logoStrapiSanity logoSanityHygraph logoHygraph

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Storyblok and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free