Storyblok, worked by an AI employee
Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Storyblok account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.
- Developer Tools
- Signs in to your account
- 10 ready-made tools
- Asked in Slack or Teams
An illustration of how the conversation reads, not a transcript from a client account.
What Storyblok is
Headless CMS with visual editor for content management and delivery across multiple platforms
You sign in with your own Storyblok account, the same way you already do. We never see or hold your password.
One message in, the work done in Storyblok.
- 01
You ask
You message your AI employee in the chat your team already has open, in one sentence, in your own words.
- 02
It works out the step
It decides what the job needs in Storyblok. You do not pick anything from a menu or wire anything together.
- 03
It does the work
Signed in to your own Storyblok account, inside the access you granted it, doing the thing you asked for.
- 04
It reports back
It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.
What it can do in Storyblok
These are the ready-made tools your AI employee already has in Storyblok. It is not limited to them, but it never has to be taught these.
- Fetch Content Type Items (GraphQL)Fetch multiple stories/content items using Storyblok's GraphQL API with filtering and pagination. Use startswith with language code prefix (e.g., 'es/', 'hi/') to retrieve translat
- 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 ContentType
- 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 dim
- Get Extension/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.
- 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 = request
- 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 an
- 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 [
- Query page items via GraphQLExecute 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,
- Retrieve Links via 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).
- Retrieve Tags via GraphQLTool to retrieve tags from Storyblok via GraphQL API. Use when you need to fetch available tags for content organization and filtering.
You stay the boss of your Storyblok account.
Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.
How we handle your data- It signs in to your own Storyblok account. You are not moving anything into ours.
- You grant access one app at a time, and you can take it back the same way.
- Everything it does in Storyblok is written down, with what it did and when.
- Anything you tell it to check with you first, it checks with you first.
It works in Storyblok and the rest of your software in the same job
A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.
Questions people ask about Storyblok
- Can an AI employee really work inside Storyblok?
- Yes. It signs in to your own Storyblok account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
- Do I have to move anything out of Storyblok?
- No. Nothing moves and nothing is replaced. Your records stay in Storyblok, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
- How does it get into my Storyblok account?
- You sign in with your own Storyblok account, the same way you already do. We never see or hold your password. You approve it before anything connects, and you can take the access back the same way you gave it.
- What can it actually do in Storyblok?
- It has 10 ready-made tools in Storyblok today, among them Fetch Content Type Items (GraphQL), Fetch GraphQL Content Item and Get Datasource Entries. The full list is on this page. It is not limited to those, but it never has to be taught them.
- Can it use Storyblok and the rest of my software in the same job?
- Yes, and that is usually the point. Reading a message in one app, checking a record in Storyblok and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
- Who decides what it is allowed to do in Storyblok?
- You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Storyblok is written down with what it did and when.