ActionStoryblokUpdated September 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.
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 run history shows the failed step with its input and the error message Storyblok returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does List Storyblok Stories support batch operations?
Run List Storyblok Stories inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Storyblok's rate limits.
More actions