Storyblok n8n integrationAutomate Storyblok with n8n.
Your Storyblok content sits behind an API call, and the workflow needs it now. The Storyblok n8n integration ships as a built-in node with 2 operations on one resource, Story: read a single entry, or list what a space holds. No Storyblok trigger exists, so the run has to start elsewhere.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Storyblok n8n integration actually give you?
The Storyblok n8n integration is a node shipped inside n8n that reads your Storyblok spaces from a workflow. It handles one resource, Story, with 2 operations: Get a story and Get many stories. You choose the space, you choose through the Source field whether the data comes from the Content API or the Management API, and n8n hands each story to the next node as a normal item other nodes can read.
Start with the case that pays for itself the fastest: the content inventory nobody keeps up to date. A Schedule Trigger, the node that starts a workflow at a fixed interval, kicks off the run, Get many stories returns the space, and the list drops into Google Sheets. Editors see what exists without opening the CMS, and nobody has to export anything by hand again.
Second case, narrower. Something in your workflow already knows a slug, the readable part of a story URL. Get a story takes that value in Identifier and returns the entry, which is enough to post a rich notification into Slack when a piece of content is referenced somewhere else. One story, one call, no copy paste.
Third case, the durable one. Teams that report on content mirror the story list into a database they control. Get many stories with Return All switched on walks the API pages until the whole space is in, and a Postgres node writes the rows. From there, reporting is just SQL, and the CMS stays the CMS.
The node covers the Story resource. When you need an endpoint the node does not expose, the HTTP Request node calls any Storyblok API endpoint and reuses the exact same credential through predefined authentication. That matters more than it sounds: you stay inside one workflow, with one stored login, instead of maintaining a script on the side.
Two things to keep in mind before building. Your credential decides what you can do, since a Content API key is read-only while a Management API key covers full CRUD. And n8n supports Content API v1 only. If you want the wider picture before committing, the n8n review covers the platform itself, and the n8n training goes through building workflows step by step.
How do you connect Storyblok to n8n?
- 01
Decide which key you need
Storyblok offers two authentication methods, and the choice is not cosmetic. A Content API key gives read-only access, which is enough for both operations in the node if you only ever read. A Management API key covers full CRUD. Pick the narrower one when reading is all you plan to do, because a key that can only read cannot do damage if it leaks into a shared workflow.
- 02
Generate the token in Storyblok
For a Content API key, open your Storyblok workspace and go to Settings > Access Tokens. Choose an Access Level of Public, which maps to
version=published, or Preview, which coversversion=publishedandversion=draft. Copy the token and enter it as the API Key. For a Management API key, open My Account > Personal access tokens, generate a token there, and enter it as the Personal Access Token. - 03
Store it once in n8n
In n8n, open the Credentials menu and create the Storyblok credential with the token you just copied. A credential is a stored login: you create it once, and every workflow you build afterwards offers it in the node dropdown. Drop a Storyblok node on the canvas, select that credential, and the Space Name or ID field loads the spaces it can reach, so you pick a space instead of typing an ID from memory.
What can the Storyblok node do?
The Storyblok node exposes 2 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Story
2 operationsGet a story
story.getWhat you see in n8n
Notes & use cases
Pulls a single entry out of a space and hands it to the next node as one item.
Key parameters
- Space Name or ID: the name of the space. Choose it from the list n8n loads, or pass an ID through an expression, the
{{ }}syntax n8n uses to read a value instead of typing it. - Identifier: the ID or slug of the story to get, often
{{ $json.field }}when the value comes from an earlier node. - Story ID: the numeric ID of the story.
- Source: where your data comes from, Content API or Management API.
Get many stories
story.getAllWhat you see in n8n
Notes & use cases
Returns the stories of a space, one n8n item per story, ready to loop over or write somewhere else.
Key parameters
- Space Name or ID: which space to read, picked from the list or given as an ID with an expression.
- Source: Content API or Management API, your call on where the data comes from.
- Return All: on, n8n chains the API pages until every story has come back; off, Limit caps the number of results.
- Starts With: under Filters, narrows the result by slug.
Need help automating Storyblok with n8n?
A person reads every message.
