ActionStoryblokUpdated June 2026

How do I list Storyblok stories?

Short answer: You can list storyblok stories in Storyblok by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Storyblok List Storyblok Stories action to a workflow, map its 0 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Storyblok Stories in Storyblok — start free
Sample request
{}
Returns
{}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List Storyblok Stories.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about List Storyblok Stories.

What does the List Storyblok Stories action do in Storyblok?
Paginated stories with filters by content type, language, tag. For sync workflows or for "build the sitemap from CMS content" patterns.
What inputs does List Storyblok Stories require?
List Storyblok Stories has no required inputs. Sensible defaults are applied if you leave fields blank.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Storyblok returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does List Storyblok Stories support batch operations?
Yes. Run List Storyblok Stories inside a Loop node to process arrays. TinyCommand handles Storyblok's rate limits automatically so you don't have to throttle manually.
More actions

Other Storyblok actions.

Action
Get Storyblok Story
Returns a story by slug or ID with full content tree. For rendering specific pages or for fetching CMS-managed content into downstream systems.
List Storyblok Stories in Storyblok — start free