Storyblok integration
No native Storyblok connector, here is what does work.
We create Storyblok stories mapped to your components, draft by default, published on your approval.
How it works
Storyblok's Management API creates stories, authenticated with a personal access token or OAuth. Stories land as drafts by default, and publishing is an explicit parameter or endpoint call, which suits a review-first workflow well. Content is structured as components, the bloks your space defines, and we map our content structure to your component schemas during setup.
Two operational details matter. Tokens are scoped to a single space, so a token from the wrong space fails with a 401 even though it is a valid token, and our connect step verifies the space explicitly. And the Management API rate-limits writes, so bulk operations from us run through a queue with backoff rather than a burst of parallel calls.
Best forTeams on Storyblok who want stories arriving as drafts in their existing component structure, ready for visual review.
Setup, step by step
- Create a personal access token in Storyblok, or authorize through OAuth.
- Add the token and your space ID to SearchHandled's Storyblok connector.
- Run the space verification, which confirms the token belongs to the space you named.
- Map your content-type components and fields to our content structure during setup.
- Choose draft-only delivery or publish-on-approval as your default.
Best practices
Review in the visual editor
Stories arrive as drafts, so your team can open each one in Storyblok's visual editor and see it rendered before publishing. Keep that step for at least the first batches while trust builds.
Keep component schemas coordinated
Our writes are shaped by your component schemas at setup. When developers change a content-type blok, tell us or rerun the mapping so new stories keep validating against the current schema.
Organize with folders and slugs deliberately
Story slugs and folder placement drive your URLs. We map the target folder and slug pattern during setup so content files into your structure instead of piling into the space root.
Let batches queue, not burst
The Management API rate-limits writes, so our bulk deliveries run through a queue with backoff. A large batch arrives over minutes rather than seconds, and every story lands.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
Tokens are space-scoped
A valid token used against the wrong space returns 401, which looks like a broken credential rather than a scoping mismatch.
How we handle itOur connect step verifies the token against the specific space you named and reports a mismatch in plain terms, so this never surfaces as a mystery failure later.
storyblok.com
Component schemas vary per space
Every space defines its own bloks, so story content that fits one space's components fails validation or renders wrongly in another.
How we handle itWe map to your content-type components and fields during setup and validate a test story against them before real publishing begins.
storyblok.com
Rate limits on bulk operations
Bursts of Management API writes hit rate limits, and naive clients drop stories or fail batches.
How we handle itOur writes run through a queue with backoff tuned under Storyblok's limits, so batch deliveries complete without loss even when they take a little longer.
storyblok.com
Questions teams ask
- Do stories publish automatically?
Only if you choose that. Stories are drafts by default, and publishing is a separate explicit action. Most teams start with draft-only delivery and move to publish-on-approval once the mapping has proven itself.
- What happens when our components change?
Stories we create are validated against the mapping from setup, so a schema change can cause validation errors on new writes. Rerun the mapping after component changes and the pipeline continues cleanly.
- Can one connection cover several spaces?
No, because Storyblok tokens are scoped to a single space. Each space gets its own connection with its own token and mapping, which also keeps content from ever crossing between spaces.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us Storyblok matters moves it up the rollout.