Publish Story

storyblok.publish_story
ActionBusiness appsconnection required

Calls the Storyblok API with the connection's credentials.

Publish a story, or only the language versions named.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Storyblok
Secret shape
the personal access token, or {"access_token": "…"}
Config it needs
base_url, region, space_id
Resolved by
config.connection_id, else node.connection_id

Configuration

3 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
space_id
Numeric id of the space to act in, from Settings → Space. Overrides the default space on the connection.
stringNo——123456
story_id
Numeric id of the story, as Storyblok reports it in a listing.
stringYes——1234567
lang
Comma-separated language codes to act on, e.g. es,pt-br. Leave empty for the whole story; per-language publishing must be enabled on the space.
stringNo——es,pt-br

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "lang": "es,pt-br",
  "space_id": "123456",
  "story_id": "1234567"
}

Output

One shape.

result

FieldTypeExample
story
The story object Storyblok returned.
object—
story_id
Numeric id of the story.
number—
uuid
The story's UUID, which the Content Delivery API uses.
string—
full_slug
The story's full slug, including its folders.
string—
published
Whether Storyblok reports the story as published.
boolean—
space_id
The space the story belongs to.
string—
action
Always 'publish' for this node.
string—
{
  "action": "",
  "full_slug": "",
  "published": false,
  "space_id": "",
  "story": {},
  "story_id": 0,
  "uuid": ""
}

See Publish Story run in a workflow.

In a technical demo we add the Storyblok connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.