Skip to content

FlowMotion

FlowMotion is Storyblok’s content operations platform. Built on n8n’s powerful engine, it connects the CMS with the rest of your tech stack and lets you automate content workflows and orchestrate AI agents.

Find out what you and your team can achieve with FlowMotion (opens in a new window), explore workflow automation ideas in a video tour, or continue reading to learn more.

Video thumbnail for "Five Workflows you should try with Storyblok's FlowMotion"

Five Workflows you should try with Storyblok's FlowMotion

FlowMotion embeds n8n within the Storyblok app, delivering seamless integration with numerous services. Within FlowMotion, you have access to custom pre-built Storyblok nodes maintained by Storyblok, so you don’t have to build from scratch. When Storyblok APIs change or new capabilities are introduced, the corresponding nodes evolve continuously.

This setup means that Storyblok handles infrastructure, uptime guarantees, scaling, and operational maintenance. You get a fully managed, single-tenant, dedicated n8n instance that turns every content event (create, update, publish, approve, translate, etc.) into an integral element in your digital ecosystem.

From content management to content operations

Section titled “From content management to content operations”

FlowMotion bridges Storyblok events with 500+ enterprise tools, turning it from a passive repository into an active, centrally governed system that injects automation directly into your content platform.

Whenever something happens in Storyblok—a story is published, an asset is updated, a translation is added, a block is created—FlowMotion goes beyond the CMS to activate a chain of events; here are a few examples of automation scenarios:

  • Open a Jira ticket to let editors know a translation is ready for review
  • Hook into a text-to-image LLM to create an open graph visual for social media
  • Email the hiring manager when a new job description is posted on the website
  • Send a Slack message to a space admin when API traffic reaches a specific threshold

The potential time-saving tasks are endless.

The main benefits of FlowMotion are governance, acceleration, and integration:

  • Enterprise security and isolation—each organization gets its own private instance, not a shared environment
  • Extended content operations platform—SSO, permissions, assets, and workflows connected directly to the CMS
  • Exclusive Storyblok nodes—leverage dozens of pre-made API endpoints designed specifically for content-driven workflows

To make the most of FlowMotion, it’s best to get familiar with a few key concepts:

  1. In n8n, an automation is called a workflow (opens in a new window).
  2. Each step within a workflow is called a node (opens in a new window).
  3. The first step that determines when the workflow runs is called a trigger (opens in a new window).

Besides supporting hundreds of 3rd-party nodes maintained by n8n and its community, FlowMotion also maps Storyblok’s Content Delivery API (opens in a new window) and Management API (opens in a new window) endpoints into nodes, offering dozens of CMS-specific triggers and actions that you can use for your automations.

FlowMotion is an organization-level feature, which means you can use it to execute workflows across spaces.

To open FlowMotion (opens in a new window), navigate to Storyblok → My Organization → FlowMotion.

Before using Storyblok’s FlowMotion nodes, you need to provide credentials (opens in a new window). Ensure you have the required Storyblok access tokens (opens in a new window), and follow the steps below:

  1. In the Overview section, select the Credentials tab.
  2. To add a new token, select Create credential in the top-left.
  3. Scroll or type Storyblok, and choose either Storyblok Content Delivery API or Storyblok Management API.
  4. Fill out the necessary details and Save.

Now, back in the Workflows tab, select Create workflow, and add nodes to construct your automation journey.

FlowMotion integrates Storyblok’s APIs as pre-built nodes, offering dozens of triggers and actions that you can use to build your own automation.

The following is a list of all native API endpoints' nodes:

Two triggers and nine actions available.

15 triggers and 59 actions available.

  • Story Published
  • Story Unpublished
  • Story Deleted
  • Story Moved
  • Datasource Entry Modified
  • Asset Uploaded
  • Asset Replaced
  • Asset Deleted
  • Asset Restored
  • User Added
  • User Removed
  • User Role Updated
  • Workflow Stage Changed
  • Pipeline Stage Deployed
  • Release Merged

Learn more about n8n and its enterprise features (available as FlowMotion add-ons) in the official docs:


Was this page helpful?

What went wrong?

This site uses reCAPTCHA and Google's Privacy Policy (opens in a new window) . Terms of Service (opens in a new window) apply.