ReddGrowReddGrow Docs
Integrations

Storyblok Integration: Publish Content Agent Articles to Storyblok

Connect Storyblok to ReddGrow with a personal access token and Space ID so each article the content agent writes is published as a Storyblok story

Once connected, the ReddGrow content agent publishes each approved article to your Storyblok space as a story. ReddGrow creates the story, publishes it, and saves the live link on the draft.

Requirements

  • A Storyblok space with a content type for your articles (for example article or blog_post)
  • That content type needs a Richtext field (or a Markdown field) to hold the article body
  • Optional: a text field whose name contains meta, description, summary or excerpt for the meta description, and one containing title or headline for the title. ReddGrow fills them when they exist
  • Your site must render stories from that content type. ReddGrow writes content into Storyblok, your frontend displays it

Get your credentials

Personal access token

  1. In Storyblok, open My account → Account settings → Personal access tokens
  2. Choose Generate New Token and give it a name
  3. Under spaces, choose Only selected spaces and pick your space
  4. Under scopes, select Stories and Components
  5. Generate the token and copy it. Storyblok shows it only once

Tokens can have an expiry date. If publishing starts failing with authentication errors, generate a new token and reconnect.

Space ID

Open your space in Storyblok. The numeric Space ID is the long number in the browser's address bar while the space is open.

ReddGrow works out your space's region (EU, US, Canada, Australia) from the Space ID, so there is nothing to pick.

Content type

The technical name of the content type block, found under Block Library. It must be a content type block, not a nestable block.

Connect in ReddGrow

  1. Go to Settings → Integrations
  2. Under Website publishing, find the Storyblok card and click Connect
  3. Fill in the form:
    • Site URL: your live site's https:// address. Used to build the link to each published story
    • Access token: the token you copied above
    • Space ID: the numeric ID of your space
    • Content type: the technical name of your article content type
    • Parent folder ID (optional): the numeric ID of a folder to publish into. Stories go to the root when empty
  4. Click Connect Storyblok

ReddGrow checks the token, the space and the content type before saving. If another platform is already connected, ReddGrow warns you that connecting Storyblok will replace it. Only one website can be connected at a time.

How publishing behaves

  • Publish creates a story with the article body, title and meta description, and publishes it right away
  • Update rewrites those same fields on the existing story and keeps any other fields your editors filled in
  • Meta description edits change only the title and meta fields of an existing story
  • Unpublish takes the story back to a draft in Storyblok. It is not deleted
  • FAQ blocks aren't supported on Storyblok, so ReddGrow skips them

The published link is your Site URL plus the story's full slug, so your frontend's routing needs to match the folder structure in Storyblok.

Troubleshooting

Connecting fails with "rejected the access token"

The token is wrong, expired, or missing the Stories and Components scopes. Generate a new one with both scopes and make sure it covers this space.

Connecting fails with "no space with that Space ID"

Check the numeric ID. It is not the space name.

Connecting fails with "no component named"

The content type name doesn't match. Use the technical name from Block Library, not the display name.

Connecting fails with "has no richtext or markdown field"

Add a Richtext (or Markdown) field to the content type, then reconnect.

The story is published but the page doesn't show it

ReddGrow only writes into Storyblok. Check that your frontend renders this content type and that its routes match the story's full slug.

Publishing fails with "too many requests"

Storyblok's Management API allows 3 requests per second on the Starter plan and 6 on higher plans. ReddGrow retries once. If it still fails, wait a moment and publish again.


Related: see the ReddGrow App guide for how campaigns, drafts, and the platform's automation pipeline fit together.