Storyblok

Let your agents read and write the content of one Storyblok space — browse stories, components (blocks), assets, tags and releases, then create, update and publish stories.

Connection

Authentication: API key (Personal access token).
Required settings:
- Region — API host of your space’s region: mapi (Europe), api-us (United States), api-ca (Canada), api-ap (Australia).
- Space ID — Storyblok → Settings → Space → Space ID (digits only).

Sign in at app.storyblok.com → My account → Account settings → Personal access tokens → + Generate New Token. Name it, set an expiration date, and under space access prefer “Only selected spaces” with the space your agents work on (“All spaces” reaches every space you own). Copy the token. The Space ID is in the space’s Settings → Space tab.See Storyblok’s documentation.

Read actions (8)

Action	Description
`get_component`	Retrieve one component by id, with its full field schema (field names, types, required, options).
`get_space`	Retrieve the connected space (name, plan, default languages, domain) — a cheap way to check the connection works.
`get_story`	Retrieve one story by id with its full content (the block tree whose root has a “component” field) — read it before update_story.
`list_assets`	List assets (media) of the space. Optional: search (file name), in_folder (asset folder id), with_tags (comma-separated), is_private (boolean), sort_by (created_at:asc\|desc, updated_at:asc\|desc, short_filename:asc\|desc), page, per_page (1-100).
`list_components`	List the components (block schemas) of the space — their names are the “component” values a story content needs. Optional: search (name or display name), is_root (true = content types only), in_group (folder UUID), sort_by, by_ids (comma-separated ids).
`list_releases`	List the releases of the space — their ids are what release_id accepts on create_story / update_story. Optional: branch_id.
`list_stories`	List stories and folders of the space (without their content). Optional: starts_with (full slug prefix, e.g. “blog/”), search (name or slug), text_search (any string in the content), with_tag (comma-separated tag names), with_parent (folder id), folder_only, story_only, is_published (booleans), contain_component (comma-separated block names), sort_by (e.g. “created_at:desc”), by_ids (comma-separated ids), in_release (release id), page, per_page (1-100, default 25).
`list_tags`	List the tags of the space — their names are what tag_list and with_tag accept. Optional: search, page, per_page (1-100).

Write actions (3)

Action	Description
`create_story`	Create a story (draft unless publish is true) or a folder. Arguments: name (string); slug (string, URL-safe, unique in its folder); content (object, required for a story, omitted for a folder: its “component” field is a content type name from list_components, the other keys are that component’s fields, e.g. {“component”:“page”,“title”:“Hello”,“body”:[]}); parent_id (optional, folder id as number or digit string, 0 = root); is_folder (optional boolean); is_startpage (optional boolean); tag_list (optional array of tag name strings); publish (optional boolean, true publishes immediately); release_id (optional release id from list_releases).
`create_tag`	Create a tag in the space. Arguments: name (string, case-insensitive, may contain spaces, unique in the space); story_id (optional, number or digit string — also assigns the tag to that story).
`update_story`	Update a story, and optionally publish it. content REPLACES the stored content: read the story with get_story first and resend the whole block tree. Arguments: story_id (number or digit string); name, slug (optional strings); content (optional object, root “component” field required); parent_id (optional folder id, 0 = root); is_startpage (optional boolean); tag_list (optional array of tag name strings, replaces the tags); publish (optional boolean — true publishes the story; false does NOT unpublish it); force_update (optional boolean, true overrides a story locked by another editor); lang (optional string, language code to publish individually); release_id (optional release id).

Permissions

Every action above must be explicitly granted to an agent before it can be used. See Permissions for the grant model and Security for how credentials are protected.

Using integrations

Communication

Scheduling

Project management

Docs & design

Files & storage

CRM & sales

Customer support

HR & recruiting

Commerce & billing

Developer tools

Observability & analytics

AI & media

Connection

Read actions (8)

Write actions (3)

Permissions

​Connection

​Read actions (8)

​Write actions (3)

​Permissions

Connection

Read actions (8)

Write actions (3)

Permissions