Skip to content
ClickRuntime

Automate Storyblok

Storyblok organises a site as stories inside spaces, built from blocks that editors change in the visual editor. ClickRuntime follows story publishing, gathers it into weekly round-ups and spots stories whose changes were never published. Say what you want to your AI assistant, read through what it will do, and it keeps running.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

Create a ClickRuntime automation: when a story is published in my Storyblok space, post its name, author and full URL to #website in Slack.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Ideas

What you can automate in Storyblok

Slack hears about each published story with its author and URL, a Friday email sums up the week, and stories with unpublished edits get chased up. These are ready-made starting points. Anything else you can describe works too.
The moment it happens

Get a Slack message for each published story

When a story goes live, Slack shows its name, who published it and where it lives on the site.

See how it works
Collects as they arrive, acts daily

Get a Friday round-up of Storyblok activity

Each Friday you get one email grouping the stories published and changed during the week.

See how it works
Weekly

Chase stories with unpublished edits

Every Monday you see stories whose changes have waited more than a month to be published.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Storyblok, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Storyblok automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Storyblok should do in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every day, list Storyblok stories that have unpublished changes for more than a week or are missing SEO fields.

When a story is published in Storyblok, post its name and URL to our #content Slack channel.

Every Monday, export Storyblok stories to Google Sheets with last edit dates, and create a Trello card for each page not updated in six months.

Beyond chat

Have Storyblok work when you're not in the chat

Connecting Storyblok to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect Storyblok

Storyblok connects with a personal access token for the Management API, generated from your own account. You also need your space ID and the region your space is hosted in.

Storyblok

CMS

  1. In Storyblok, open My Account and go to Personal access tokens.
  2. Choose Generate, name the token, and copy it.
  3. Note your space ID and region (EU, US, AP, CA or CN) from the space settings.
  4. Save the token as a secret on Connections & secrets in the ClickRuntime dashboard, along with the space ID and region.

Good to know

Storyblok limits that affect automations

  • The Management API allows 3 requests per second on the Starter plan and 6 on Growth and higher plans. An automation that reads many stories has to pace itself within this.
  • Personal access tokens are sent without the Bearer prefix, unlike OAuth tokens.
  • Each region has its own API address, so the region of your space must match the connection.
  • Storyblok does not retry webhooks. If a delivery fails, that publish event is not sent again.
  • Only a space owner or admin can set up webhooks, and the number of webhooks per space is limited.

FAQ

Questions about automating Storyblok

What does ClickRuntime use my Storyblok token for?
To read stories in the space you name: their names, authors, URLs, publish state and when they were last changed. The automations here only read; they do not edit stories.
Why does it need my space region?
Storyblok hosts spaces in separate regions, each with its own API address. Requests sent to the wrong region fail.
Are publish notifications real-time?
Yes. A Storyblok webhook tells ClickRuntime when a story is published. Storyblok doesn't retry failed deliveries, so the weekly digest is a useful backup.
Can I use a delivery access token instead?
Space access tokens only read published content through the delivery API. Spotting unpublished changes needs the Management API, which uses a personal access token.
Do I need AI or an AI key?
Not for these automations. If you later want summaries of what changed, the AI included with every ClickRuntime plan covers it, so no AI key is needed.
Is this a Storyblok connector for ChatGPT or Claude?
Not for chatting with Storyblok data. A chat connector lets your assistant read and change Storyblok while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Storyblok event.

Related pages

Keep exploring

Tell your assistant what Storyblok should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude