CMS

Storyblok

Storyblok is a headless CMS: content lives as stories inside a space, shaped by components you define, with images and files kept as assets.

Authentication

  • API key

Actions

Generic API request. Call any Storyblok API endpoint on this connection, for the case where no shipped action covers it yet. The connection supplies the base URL, the authentication and the egress route, so only the path, query and body are yours to fill.

  • Create storyCreate a content entry (a Story) inside a Space.
  • Delete storyDestructiveDelete a Storyblok Story by id (DELETE /spaces/{spaceid}/stories/{storyid}).
  • Get storyRead one content entry by id, scoped to its Space - the management-API read, which returns the stored story rather than a published rendering.
  • List assetsList assets in a Storyblok Space (GET /spaces/{spaceid}/assets) with optional page pagination.
  • List componentsList all component (block) definitions in a Storyblok Space (GET /spaces/{spaceid}/components).
  • List spacesList the Storyblok Spaces the connected personal access token can reach, each with its numeric id and name - the id every other Storyblok action needs in its path (GET /spaces).
  • List storiesList Stories in a Storyblok Space (GET /spaces/{spaceid}/stories) with optional page/perpage/startswith filters.
  • Update storyDestructiveUpdate a Storyblok Story (PUT /spaces/{spaceid}/stories/{storyid}, JSON body wrapped as {story:{...}}).

Triggers

  • New or updated assetStarts when an asset in a Storyblok Space is uploaded or its details change.
  • New or updated componentStarts when a component (block) definition in a Storyblok Space is created or changed.
  • New or updated storyStarts when a story is created or edited in the connected Storyblok space, across both draft and published content.
  • Story published (webhook)Starts the moment a story is published in the connected Storyblok space, delivered by a webhook instead of polling the story list.

Product names, logos and brands are the property of their respective owners and are used here for identification only. Their use does not imply endorsement by, or affiliation with, those owners.