Storyblok Integration
Connect Storyblok to Arahi's no-code AI agents and automate workflows in minutes.
About the Storyblok integration
Headless & API-based CMS with an opt-in head With Arahi AI, you can connect Storyblok to Blogger, Clockify, Cloud Convert and 1,500+ other apps using AI-powered workflows. No coding required — set up triggers, actions, and intelligent automation in minutes.
- Category
- Productivity
- Authentication
- keys
Storyblok automation use cases
- Meeting notes → action items
- Extract tasks from Storyblok pages or docs and push them to your project tracker.
- Document ingest to knowledge base
- Centralize scattered docs into Storyblok with auto-tagging and cross-links as they're added.
- Recurring task automation
- Spin up weekly or monthly Storyblok task templates without copy-pasting from last cycle.
- Approval routing
- Route Storyblok documents through an approval chain with reminders and escalation.
Storyblok workflow examples
- Rebuild Vercel on Storyblok publish
Storyblok publish events call a Vercel deploy hook to rebuild the Next.js frontend, shipping editor changes without a developer run.
Storyblok entry published then Vercel deploy hook fires.
- Fetch Content Type Items into Google Sheets
A schedule calls Fetch Content Type Items from Storyblok and writes entries into a Google Sheets content inventory, giving editors a searchable audit surface outside the headless CMS.
Daily cron fires then Fetch Content Type Items logged to Google Sheets.
- Post Get Page Item previews to Slack
Storyblok draft saves call Get Page Item and post a preview URL into a Slack content channel for editorial review before publish.
Storyblok draft saved then Get Page Item preview posted to Slack.
Storyblok actions
- 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.
- Fetch GraphQL Content Item
- Tool 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.
- 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.
- Get Datasource Entries
- Tool 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.
- Get GraphQL Rate Limit
- Tool 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).
- Get Page Item
- Tool 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.
- List GraphQL Content Type Items
- Tool 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.
- 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.