STORYBLOK n8n INTEGRATION: AUTOMATE STORYBLOK WITH N8N
STORYBLOK N8N INTEGRATION: AUTOMATE STORYBLOK WITH N8N
Need help automating Storyblok with n8n?
Our team will get back to you in minutes.
Why automate Storyblok with n8n?
The Storyblok n8n integration gives you access to 2 actions that cover the essential content retrieval operations: fetching a single story or retrieving multiple stories at once. These actions form the backbone of any content automation strategy, allowing you to pull structured content from your CMS and route it wherever it needs to go.
Significant time savings are immediate. Instead of manually exporting content from Storyblok to feed other systems—your email marketing platform, your analytics dashboard, your translation service—you set up the flow once and let n8n handle the rest. Content teams can focus on creating rather than copying and pasting between tools.
Seamless integration is where this combination truly shines. n8n connects to over 400 applications, meaning your Storyblok content can flow directly into Slack notifications, Google Sheets for editorial calendars, Notion databases, Mailchimp campaigns, or custom webhooks for your proprietary systems. The possibilities expand dramatically when your CMS talks to everything else.
Concrete use cases include: content syndication (automatically pushing new stories to social media schedulers), editorial dashboards (pulling story metadata into spreadsheets for oversight), localization workflows (fetching stories to send to translation APIs like DeepL), and backup automation (regularly retrieving all content for archival purposes).
How to connect Storyblok to n8n?
! 1 stepHow to connect Storyblok to n8n?
- 01
Add the node
Search and add the node in your workflow.
TIP💡 TIP: Create separate API tokens for different environments (staging vs. production) and name your n8n credentials accordingly. This prevents accidental content pulls from the wrong Storyblok space and makes debugging much easier when workflows don't behave as expected. If you encounter issues, check our n8n troubleshooting guide for common solutions.- 01
Need help automating Storyblok with n8n?
Our team will get back to you in minutes.
Storyblok actions available in n8n
01 Action 01Get Many
This action is your go-to for batch content retrieval. It fetches multiple stories from your Storyblok space in a single operation, making it ideal for content synchronization, bulk exports, and building editorial overviews across your entire CMS.
Key parameters:
- Credential to connect with: A required dropdown to select your Storyblok authentication. Choose the appropriate account if you have multiple spaces configured.
- Resource: A required dropdown set to "Story", defining that you're working with Storyblok story entries.
- Operation: Set to "Get Many" to retrieve multiple stories at once.
- Return All: An optional toggle switch. When enabled, it fetches every available story, ignoring any limit. Useful for full exports but can be slow for large content libraries.
- Limit: An optional number field (default: 50) that caps how many stories are retrieved. Only active when "Return All" is disabled.
- Filters: An optional section to add conditions and refine which stories are retrieved—useful for targeting specific folders, tags, or content types.
Common use cases:
- Pulling all blog posts weekly to generate an automated newsletter digest
- Syncing product stories to an external e-commerce platform
- Building a content audit spreadsheet by retrieving all stories with their metadata
- Feeding story data into a translation API for localization workflows
Use this action when you need to process content in bulk or when the specific story ID isn't known in advance.
02 Action 02Get Story
This action retrieves a single, specific story from Storyblok using its unique identifier. It's perfect for targeted content operations where you know exactly which piece of content you need—whether triggered by a webhook, a user action, or another upstream node in your workflow.
Key parameters:
- Credential to connect with: Required dropdown to select your Storyblok account credentials.
- Resource: Set to "Story" to target Storyblok story entries.
- Operation: Set to "Get" for single-item retrieval.
- Identifier: A required text field where you provide the unique ID or slug of the story to fetch. This can be hardcoded or dynamically passed from a previous node (e.g., from a webhook payload or a spreadsheet row).
Common use cases:
- Fetching full story content when a webhook notifies you of a content update
- Retrieving a specific product page's content to sync with inventory systems
- Pulling article data to automatically post to social media upon publication
- Getting story details to populate a custom notification or approval request
Use this action when your workflow targets a known story and you need its complete content and metadata for downstream processing.
Build your first workflow with our team
Drop your email and we'll send you the catalog of automations you can ship today.
- Free n8n & Make scenarios to import
- Step-by-step setup docs
- Live cohort + community support
Frequently asked questions
Is the Storyblok n8n integration free to use?
Yes, the Storyblok integration is included natively in n8n at no additional cost—whether you're using n8n Cloud or the self-hosted community edition. You'll need a Storyblok account with API access, which is available on all Storyblok plans including their free tier. The integration uses Storyblok's Content Delivery API, which has rate limits based on your Storyblok plan. For high-volume automations, ensure your Storyblok subscription supports the request volume you anticipate.Can I filter which Storyblok stories are retrieved in n8n?
Absolutely. The "Get Many" action includes a dedicated Filters section where you can add conditions to refine your results. You can filter stories by folder, by specific content type, by publication status, or by custom fields you've defined in your Storyblok schema. This is particularly useful when you only want to sync published blog posts, retrieve stories from a specific folder for localization, or target content with particular tags. Simply click "Add Filter" in the node configuration and define your criteria. For more complex filtering needs, explore the Storyblok Content Delivery API documentation.How long does it take to set up the Storyblok n8n integration?
Most users complete the initial setup in under 5 minutes. Retrieving your API token from Storyblok takes about a minute, and configuring the credentials in n8n is straightforward. Building your first working workflow—say, fetching stories and sending them to a Google Sheet—typically takes 10-15 minutes if you're familiar with n8n basics. The hardest part is usually deciding what to automate first, not the technical configuration itself. If you're new to n8n, consider starting with our downloadable automation catalog for inspiration.
