Storyblok configuration
Configuration fields for the Storyblok integration.
Configuration follows the common integration setup.
| Field | Description |
|---|---|
| Region | eu, usa, canada, australia, or china (case-sensitive). Each maps to its own API host, so the value must match where the space lives. A full Storyblok API URL can be entered instead. |
| Space ID | Identifier of the space receiving content. |
| Management API token | Token sent as the Authorization header on every request. |
| Root folder | One folder per entity type: products, categories, collections, brands, and series. Content is created inside its matching folder, so each folder ID must exist before use. |
| Rate limit | Requests per second to Storyblok. |
| Sync scope | Events Enad reacts to: products, collections, categories, brands, and series. |
| Include translated slugs | Sends translated slugs for every story write. |
| Flatten tree | Ignores the Enad category hierarchy. Every category and collection is created directly under the root folder and uses the Enad ID as the slug. |
| Brands as folders | Creates brands as a folder plus a startpage story. Otherwise a brand is a single story. |
| Series as folders | Creates series as a folder plus a startpage story. Otherwise a series is a single story. |
Stories, folders, and startpages
A category or collection with children is stored as a Storyblok folder with a startpage story inside it. The startpage holds the content. A category or collection without children is stored as a plain story.
When Enad moves content under a parent that is currently a plain story, the integration converts that parent into a folder: it creates the folder, moves the old story into it as its startpage, and gives the story a temporary slug. Startpage slugs are never rewritten afterwards, so links to them keep working; only the folder’s slug is updated on later renames. Deleting a startpage deletes the parent folder instead. The configured root folder for a type is never deleted.