Workflow Builder: open‑source AI workflow orchestration
Your cases run for weeks, wait for a person, and never get lost. Each step is your code,
an AI agent, or a human decision.
Free 30-minute call
PRODUCTS BUILT WITH WORKFLOW BUILDER

Plura AI
Familiar situations
Where long-running workflows with a human in the loop get stuck
Your core systems are too costly to rewrite. The business still wants AI agents and new workflows within months.
Nobody can say where a case stands
A customer asks a bank about a loan application. Support cannot see which step the application has reached or who acts next.
AI stays in the pilot
An insurer wants AI agents to take routine claims work. The agent works in a demo, but nobody signs off on a workflow that cannot be seen, checked, or handed to a person.
Every change waits for the next release
One new step in an insurer's claims handling waits for the software vendor's next release. A small change becomes a ticket and a queue.
Same situations
What changes when your workflows run on Workflow Builder
Your team gets a record of every case, AI steps that stay on the drawn path, and changes built from existing blocks.

Nobody can say where a case stands
Every case has a record and a final state
With Workflow Builder: each case keeps a record of every step and decision, and ends completed, failed, or cancelled. AI Studio, the open-source demo app, draws each case step by step on a diagram.

AI stays in the pilot
AI agents do the work and the diagram decides the path
With Workflow Builder: an AI step runs inside the path drawn on the diagram. The AI agent drafts the result, and the case waits until a person decides.

Every change waits for the next release
A change from existing blocks ships without a release
With Workflow Builder: your developers define each block – a reusable step type – once. After that, steps and conditions change without code and without a new release of your app.
What you get
How Workflow Builder works: Runtime, Editor, and Temporal
Three layers sit over the systems you already run, and none of those systems has to be replaced.
Core
Workflow Builder Runtime
Each workflow lives in the Runtime. The Runtime takes a case from the first step to a final state and keeps decisions, retries, versions, and the case record. Each step is one of three kinds. AI steps are optional, and the model can run inside your network.
See how the parts fit together – README on GitHub
Surface
Workflow Builder Editor
The canvas where a workflow is drawn and changed. Your developers embed the Editor in your product as a React component.
Durable execution engine
Temporal
Temporal is open source and runs underneath the Runtime. After a failure or restart, a case continues instead of starting over. Your engineers can connect another engine through an adapter.
Base
Your systems
Your developers connect each system once, as a reusable block. Workflow Builder has no catalog of ready-made connectors. Through the Workflow Builder MCP (Model Context Protocol) server, an AI coding assistant looks up the docs and real function signatures before writing a block.

Build or start
What your team no longer has to learn in production
AI coding tools write a working demo fast. The months go into the cases that show up only after real people use the workflow.
Building from scratch
Starting from Workflow Builder
Edge cases that only show up in production
Building from scratch
A decision arrives twice. A release goes out while cases wait. A server restarts mid-case. Your team learns each one from an incident.
Starting from Workflow Builder
A waiting case survives server restarts and new releases, for days or weeks. The first decision counts, a duplicate is refused, and the person gives a reason.
Changes while cases are in progress
Building from scratch
Your team decides what happens to open cases when a workflow changes, then builds the versioning.
Starting from Workflow Builder
Open cases finish on the version they started with. New cases follow the change.
Editor that looks like your product
Building from scratch
Your front-end team builds the canvas, panels, and validation before anyone draws a workflow.
Starting from Workflow Builder
Design tokens match the Editor to your product, under your own brand and in your users' languages.
Fixes and upgrades after launch
Building from scratch
Each fix and upgrade is your team's job for as long as the workflows run.
Starting from Workflow Builder
Workflow Builder updates ship in the public repository on GitHub. Your backend and worker code stay with your team.
Where to start
Pick the starting point closest to your situation
Teams come to Workflow Builder from three situations: core systems that stay in place, Temporal as the engine, or a product customers already use.

You run claims, lending, or orders on systems you will not replace
Workflow Builder sits on top of your core systems. Your developers connect each system once as a block, and every case runs to a final state, with AI steps and human decisions where your team wants them.

You run Temporal, or plan to
Temporal runs the code your developers write. The Workflow Builder Runtime adds the layer above: each workflow stored as data and changed without code, a built-in step that waits for a person, versions, and a record of every case. An AI agent becomes one more step, and the case still reaches a final state.

You want a workflow editor inside your product
Your customers design and change workflows inside your app, AI steps included. The Workflow Builder Editor installs as a React package and needs no engine: each workflow is saved as JSON for your code. Add the Runtime when drawn workflows have to last and wait for people.
Customer stories
What teams got from building on Workflow Builder
Each story shows what a team built on Workflow Builder and, where the customer has published one, the result.
Visual campaign builder for large business clients
On Workflow Builder
Vercom built a visual campaign builder for large business clients on Workflow Builder.

White-label editor inside an AI product
What changed
The workflow UI shipped in 1 day.

From change requests to an AI automation layer
Starting point
Every change to a claims workflow at one of the vendor's customers was a change request and weeks of waiting.
On Workflow Builder
An AI automation layer over the core platform, on Workflow Builder and Temporal.
Document workflows that wait for people
On Workflow Builder
Workflows for the documents insurers send. Each case waits for a person or for more documents and survives deployments.
Workflow Builder gave us a complete, proven foundation. Our team went straight to building what is unique about our product. That saved us roughly EUR 50,000 and months of trial and error.
Adam Lewkowicz, CTO, Vercom
Two roads to launch
Run Workflow Builder yourself or together with its creators
Both roads run on the same open-source code. The second adds the engineers who created Workflow Builder.
Run Workflow Builder yourself
Run Workflow Builder with its creators
Fits you when
Run Workflow Builder yourself
Your engineers have time to deploy and run the whole setup.
Run Workflow Builder with its creators
You want the result without pulling engineers off other work, or one team answerable for the outcome.
First step
Run Workflow Builder yourself
Install the Editor from npm with the quick start.
Run Workflow Builder with its creators
A free 30-minute call, then your first workflow mapped together. The Workflow Builder engineers ask the questions that usually surface only in production.
First result
Run Workflow Builder yourself
Your first workflow, built by your engineers at your own pace.
Run Workflow Builder with its creators
Your first workflow, built in your repository with an engineer from the Workflow Builder team – working software to show management.
Before launch
Run Workflow Builder yourself
Your engineers add login and separate data between customers.
Run Workflow Builder with its creators
Workflow Builder engineers add login and data separation with yours and review security and architecture.
After launch
Run Workflow Builder yourself
The docs, GitHub issues, Discord, and the MCP server for your AI coding assistant.
Run Workflow Builder with its creators
Support under a service-level agreement (SLA) and a named engineer.
On both roads, Workflow Builder stays open source under Apache 2.0, which allows commercial use and embedding in a product you sell. Code written for your project lives in your repositories and belongs to your organization, and SLA support is a separate agreement.
Hands-on start
Try Workflow Builder yourself with your AI coding assistant
No meeting needed. The Workflow Builder MCP server gives your AI coding assistant the docs and the API before the first line of code.
Give your AI coding assistant the docs and API
The Workflow Builder MCP server lets your assistant look up real function signatures before writing code. The docs and API data ship inside the package, so the server needs no account or API key and makes no network calls. Works with Claude Code, Claude Desktop, Cursor, VS Code, and OpenAI Codex.
@workflowbuilder/mcp on npm
Put Workflow Builder Editor in your React app
The Editor is a React component built on React Flow.
Follow the quick start
Run Workflow Builder on Temporal workers
The Temporal plugin, an npm package, connects Workflow Builder to the workers your team runs.
Read the setup steps in the plugin README
Watch a sample workflow run in AI Studio
AI Studio draws each step of the sample on the diagram. A local run follows the repository README; AI steps need your model key.
Open AI Studio

FAQ
Questions people ask about Workflow Builder
Short answers on how Workflow Builder fits your stack, where your data goes, and what the license allows.
- What is Workflow Builder?
Workflow Builder is an open-source AI workflow orchestration framework for cases that run for weeks. Each step is your code, an AI agent, or a person, and every case reaches a final state. Workflow Builder runs on Temporal.
- How is Workflow Builder different from using Temporal alone?
Workflow Builder is an AI workflow orchestration framework on top of Temporal, and Temporal is the durable execution engine that runs code your developers write. Workflow Builder stores each workflow as data that changes without code, and adds a built-in step that waits for a person, versions, and a record of every case. The Workflow Builder Editor alone runs without Temporal.
- How does Workflow Builder compare to n8n?
Workflow Builder becomes part of your product, which is the main difference from n8n. The Workflow Builder Editor runs in your app under your brand, and cases run for weeks on Temporal.
- How does human in the loop work in Workflow Builder?
In Workflow Builder, a human-in-the-loop step pauses a case until a person decides, for example on a result drafted by an AI agent. The case can wait days or weeks and survives server restarts and new releases.
- Which AI models can I use with Workflow Builder?
Workflow Builder works with any model that has an OpenAI-compatible API, including one inside your own network or in an air-gapped setup. Workflows with no AI steps run the same way.
- Does Workflow Builder have an MCP server for AI coding assistants?
Yes. The @workflowbuilder/mcp package is a Model Context Protocol (MCP) server. The server gives an AI coding assistant the Workflow Builder docs and public API, so the assistant checks real signatures before writing code.
- Where does my data go when Workflow Builder runs?
Workflow Builder keeps data on your infrastructure when Temporal is self-hosted and the AI model runs inside your network. With Temporal Cloud or an external AI model, data also goes to those services.
- Is Workflow Builder open source, and what does Apache 2.0 allow?
Yes. Workflow Builder is open source under the Apache 2.0 license, which allows commercial use, code changes, embedding in a product you sell, and white-labeling. Code written for your project belongs to your organization.
- Do I need developers to use Workflow Builder?
Yes, for setup: developers define each block type as a JSON Schema. After that, steps and conditions change without code, inside the developers' rules.
