Storyblok

· پراستفاده‌ترین #366

Your headless CMS, written by agents not editors

Marketingبهره‌وریاسنادDeveloperاتوماسیون

Storyblok is a headless CMS built around a visual editor — teams author structured content in stories, components, and asset libraries that any front-end can consume via its delivery API. Connect it to Actionist and your agents can publish campaign pages the moment a deal closes, update pricing stories the instant a rate card is approved, list and audit every story or component schema without a human opening a browser tab, and trigger preview deploys so stakeholders review on real infrastructure before content goes live.

میانگین زمان صرفه‌جویی‌شده
10 ساعت
برای هر نفر · در هر ماه
تقریبا 1 روز کاری برگشتی

کار دستی را حذف می‌کند. Agents eliminate the manual cycle of opening the CMS, finding the right story, filling in fields, clicking publish, and notifying stakeholders — every step that used to require a human in front of a screen.

زمان‌بندی

عامل Storyblok شما چه چیزهایی را خودکار اجرا می‌کند

یک هفته کارهای زمان‌بندی‌شده که عامل Actionist از طرف شما اجرا می‌کند.

28کارهای زمان‌بندی‌شده
7عامل‌های فعال
24/7همیشه روشن
عامل‌ها
چهارشنبهجمعه
چهارشنبه
پنجشنبه
جمعه
7a
8a
9a
10a
11a
12p
1p
2p
3p
4p
5p
6p
گردش‌کارهای چنداپلیکیشنی

Storyblok × همه اپلیکیشن‌های دیگر شما

اتوماسیون‌های سرتاسری که چند اپلیکیشن را به هم وصل می‌کنند؛ هرکدام یک خروجی واقعی کسب‌وکار.

6گردش‌کارها
9اپلیکیشن‌های درگیر
حدود 43 ساعتصرفه‌جویی در هفته
6نقش‌های پوشش‌داده‌شده
برای موفقیت مشتری
ویژه4 اپلیکیشن

Self-serve knowledge base, always fresh

When a customer emails a question that matches an existing Storyblok knowledge-base story, your agent fetches the live article, formats a personalised reply, and posts it to Slack so the CSM can send it with one click — no copy-paste, no tab-switching. It then unpublishes any outdated version of that article if the content has changed, publishes the refreshed story, and schedules a Google Calendar reminder to review the article again in 90 days. Support quality goes up; response time drops below three minutes.

حدود 13 ساعت

زمانی که تیم شما هر هفته و به‌صورت خودکار پس می‌گیرد

جریان کار
تریگر·When a customer support email arrives with a question matching a tagged Storyblok knowledge-base article
نتیجه
Publish refreshed story versionPost formatted reply to CSM with article linkSchedule 90-day article review reminder
برد اصلی
صرفه‌جویی در هر اجرا
حدود 1 ساعت
اجرا در هفته
~10×
Consistent, on-brand support answers every time
اجرا توسطCustomer Support Agent
بازگشت سرمایه

صرفه‌جویی

چیزی که تیم شما پس می‌گیرد: کارهای دستی‌ای که حذف می‌شوند و ارزشی که ایجاد می‌شود.

بدون Actionist

کاری که امروز دستی انجام می‌دهید

با Actionist

کاری که عامل شما برایتان اجرا می‌کند

  • Sales
    18 دقیقه در هفته
    Manual case-study fetch

    Reps spend 18 minutes per request searching the CMS, copying URLs, and formatting case-study links before each demo call.

    عامل Sales
    ۰ دقیقه
    Agent builds a personalised story

    Agent lists matching case studies by industry tag, creates a personalised landing page story, and posts the live URL in Slack before the rep's next meeting.

  • Marketing
    13 دقیقه در هفته
    Manual publish scheduling

    Marketers set alarms to be online at publish time, then manually open Storyblok, find the story, and click publish — a 13-minute routine per content drop.

    عامل Marketing
    ۰ دقیقه
    Agent publishes on schedule

    Agent reads the content calendar, validates required fields, and publishes each story at the exact scheduled timestamp — no human needs to be at their desk.

  • Customer Support
    18 دقیقه در هفته
    Knowledge-base article hunt

    CSMs spend 18 minutes per ticket searching Storyblok for the right knowledge article, then reformatting and pasting it into their reply.

    عامل Customer Support
    ۰ دقیقه
    Agent surfaces and refreshes the article

    Agent matches the customer question to a tagged knowledge-base story, publishes the latest version, and posts the formatted answer to Slack in under 10 seconds.

  • Human Resources
    7 دقیقه در هفته
    Policy page update lag

    HR spends 7 minutes each time a policy changes: finding the right story, editing the body, and publishing it — a process that often sits in a backlog for days.

    عامل Human Resources
    ۰ دقیقه
    Agent syncs policy content instantly

    When an approved policy document changes in Notion, the agent updates the matching Storyblok story and publishes it in under 30 seconds, keeping the employee-facing page current.

  • Finance
    13 دقیقه در هفته
    Pricing page manual refresh

    Finance waits on a developer or editor to update pricing stories after each rate approval, a 13-minute round-trip that risks periods of inaccurate public pricing.

    عامل Finance
    ۰ دقیقه
    Agent updates and publishes rate changes

    The moment a pricing table is approved in Notion, the agent updates all product stories and publishes them — accurate pricing is live before the approval email is read.

  • Operations
    25 دقیقه در هفته
    Content inventory audit

    Ops manually lists all stories folder by folder, copies slugs into a spreadsheet, and cross-checks publish status — a 25-minute recurring task that always feels behind.

    عامل Operations
    ۰ دقیقه
    Agent runs the audit automatically

    Agent lists all stories with filters for type, folder, and status, then writes the full inventory to a Google Sheet — operations has an up-to-date content map every Monday without lifting a finger.

  • Legal
    6 دقیقه در هفته
    Compliance page withdrawal

    When legal flags a page for review, the team waits 6 minutes for an editor to find and unpublish the story, during which the non-compliant content stays live.

    عامل Legal
    ۰ دقیقه
    Agent unpublishes in seconds

    When legal raises a compliance flag, the agent immediately unpublishes the story and notifies the editor in Slack — the page is offline in under 10 seconds, not 6 minutes.

+ صدها اتوماسیون دیگر Storyblok
میانگین ماهانه
10 ساعت / نفر / ماه
میانگین ماهانه
10 ساعت / نفر / ماه
محاسبه‌گر

محاسبه کنید تیم شما چه چیزی ذخیره می‌کند

اندازه تیم
10 نفر
نرخ ساعتی
20 دلار / ساعت
ساعت ذخیره‌شده / هفته
25
ساعت ذخیره‌شده / سال
1,250
بازگشت سالانه
$25,000

بر اساس الگوی رایج استفاده تیمی از Storyblok: کارهای قابل مشاهده به‌علاوه چند اتوماسیون دیگر که عامل اجرا می‌کند: حدود2.5 ساعت / نفر / هفته کار اداری خودکار می‌شود.

اتصال

چطور Storyblok را به Actionist وصل کنید

روش اتصالی را انتخاب کنید که با محیط کاری شما سازگار است.

The fastest path to Storyblok. Install the hypescale/storyblok-mcp-server in one step and your agent gets access to 160 tools across 30 modules — stories, components, assets, spaces — with no API token to rotate or scope to misconfigure.

1
Open the Apps tab

Find Storyblok in the Apps library and click Connect. MCP is selected by default.

2
Authorise in Storyblok

Actionist opens the Storyblok OAuth screen. Select the space(s) you want the agent to access and approve the permission scopes — read, write, and publish as needed for your workflows.

3
Test the connection

Actionist runs a read-only call to verify the handshake. You're ready.

اکشن‌ها

15 اکشن که عامل شما می‌تواند اجرا کند

عملیات خواندن و نوشتنی که برای عامل Actionist شما در دسترس است.

تریگرها

7 رویداد که عامل شما می‌تواند به آن واکنش نشان دهد

رویدادهایی که عامل شما زیر نظر می‌گیرد و در پاسخ به آن‌ها اکشن اجرا می‌کند.

مهارت‌ها

مهارت‌هایی که با Storyblok خوب کار می‌کنند

مهارت‌های قابل استفاده مجدد عامل که کنار این اپلیکیشن مفید هستند.

هنوز مهارت جفت‌شده‌ای آماده نشده است. این اپلیکیشن را به عامل خود اضافه کنید تا گزینه‌های مناسب را کشف کنید.
سرورهای MCP

سرورهای MCP سازگار با Storyblok

Actionist را به سرورهای MCP ساخته‌شده برای این اپلیکیشن یا پیرامون آن وصل کنید.

hypescale/storyblok-mcp-server

Community MCP server exposing 160 tools across 30 Storyblok modules — stories, components, assets, spaces, datasources, and more — giving agents full Management API coverage without custom integration work.

پرسش‌ها

پرسش‌ها درباره Storyblok + Actionist

How do I connect Storyblok to Actionist?
The fastest method is MCP: open the Apps tab, find Storyblok, click Connect, and complete the OAuth handshake to select your space. Your agent gains access to 160 tools — stories, components, assets, spaces — immediately. If you only need read access, paste a Content Delivery API token from Storyblok → Settings → API-Keys instead. MCP is recommended because it handles permission scoping automatically and requires no token rotation.
What credentials does Actionist need for full read and write access?
For full CRUD operations — creating, updating, publishing, and deleting stories — use the Management API key found in Storyblok → Settings → API-Keys. The Content Delivery API key only supports reads on published content. Via MCP, you grant write scopes during the OAuth flow and Actionist handles the credential lifecycle. Never share your Management API key beyond Actionist; treat it as you would a root password.
Can I combine Storyblok with other tools in a single workflow?
Yes — Actionist workflows routinely chain Storyblok with tools like Slack, HubSpot, Google Sheets, Notion, GitHub, and Stripe. A typical pattern: a HubSpot deal close triggers the agent to publish a Storyblok landing page and open a GitHub QA issue in the same run. Any action in Storyblok can feed data into or receive data from any other connected app, with no separate middleware required.
What can agents actually do inside Storyblok?
Agents can read individual stories or list them filtered by content type, folder, language, or tag; create new stories from any schema; update content fields programmatically; publish or unpublish on a schedule; delete stories; manage component schemas; list and upload assets; retrieve space metadata; and trigger preview deploys. The MCP server exposes 160 tools across 30 modules, covering virtually every Storyblok Management API endpoint.
How do I avoid accidentally publishing content the agent is still drafting?
Keep authoring and publishing as separate explicit steps in your workflow. The agent calls 'Update story' to write fields, then only calls 'Publish a story' after a human-approval step or a conditional check confirms all required fields are filled. You can also validate content via 'Get a story' and inspect field completeness before the publish call — build the gate into the workflow and the publish action never fires on incomplete content.
How do I target specific spaces, languages, or content types in my workflows?
Every Storyblok API call accepts filter parameters: filter by content type name to target only 'blog-post' or 'product-page' stories; filter by starts_with to scope to a folder path; pass a language code to retrieve locale-specific content. The agent threads these parameters from upstream workflow data — for example, reading the language from a deal record before fetching the matching translation. No hard-coded filters needed.
How does the preview deploy action work, and who can access the staging URL?
Triggering a preview deploy kicks off a build of your connected front-end framework (Next.js, Nuxt, etc.) using Storyblok's preview token, which includes draft content. The resulting URL is shareable to anyone you send it to — no Storyblok account required. Preview URLs typically expire after a set time defined by your hosting provider. The agent can post the URL to Slack, attach it to a calendar event, or email it to a client as part of an approval workflow.
What happens if a Storyblok API call fails mid-workflow?
Actionist surfaces the error with the Storyblok API response code and message, then stops the workflow at the failing step. Partial writes — for example, updating three stories before a fourth fails — are not automatically rolled back, so design workflows to be idempotent: re-running them from the failed step should produce the same result without duplicating data. For bulk operations, test with a small folder filter first to confirm the pattern before running across an entire space.