Skip to content
Esc
↑↓navigate↵open⌘Jpreview
On this page

Storyblok events

Events the Storyblok integration handles and what each does.

The integration mirrors Enad products, categories, collections, brands, and series into Storyblok stories. Each event group can be turned on or off in the integration settings, and every story and folder carries enad_id, which is how existing items are matched.

Products

Event What Enad sends
Product created A story with the product slug and name, plus translated slugs. Products with the draft status are not created.
Product updated Updates name, slug, and translated slugs of the existing story, or creates it when none exists.
Product status changed The story publishes when the Enad status is active and unpublishes otherwise.
Product deleted Deletes the story. A story that is already gone counts as deleted.

No body content, images, prices, or attributes are included.

Categories and collections

Event What Enad sends
Category or collection created A story or folder following the folder and startpage model described on the configuration page, with name, slug, translated slugs, and parent structure. A category that exists as neither story nor folder is created. Categories in draft fail on create.
Category or collection updated Updates the existing story or folder.
Category or collection deleted Deletes the story or folder.

Brands and series

Event What Enad sends
Brand upsert A story with name, slug, logo URL, and cover URL.
Serie upsert A story with name, slug, and the brand parent.
Brand or serie deleted Deletes the story.

Brands and series are always published.

Field mapping

Enad data Storyblok destination
Product ID enad_id content field
Product name Story name
Slug Story slug, translated slugs per language
Product relations Product stories with translated names, nested under the parent
Brand logo Brand story content field
Brand cover Brand story content field
Folder structure Products folder at the root, with Brands and Product folders inside