<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Dominika Pacholec</title>
    <description>The latest articles on DEV Community by Dominika Pacholec (@dominika_pacholec).</description>
    <link>https://dev.to/dominika_pacholec</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4031776%2F92a376ab-3551-4631-bf8a-46ed2ca0eb6b.jpg</url>
      <title>DEV Community: Dominika Pacholec</title>
      <link>https://dev.to/dominika_pacholec</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/dominika_pacholec"/>
    <language>en</language>
    <item>
      <title>How deeply can you configure How deeply can you configure a workflow editor? The palette, panels, and theme are data</title>
      <dc:creator>Dominika Pacholec</dc:creator>
      <pubDate>Thu, 12 Nov 2026 11:09:21 +0000</pubDate>
      <link>https://dev.to/workflowbuilder/how-deeply-can-you-configure-how-deeply-can-you-configure-a-workflow-editor-the-palette-panels-1jh0</link>
      <guid>https://dev.to/workflowbuilder/how-deeply-can-you-configure-how-deeply-can-you-configure-a-workflow-editor-the-palette-panels-1jh0</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcuzasyld0zxr1p79lzf1.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcuzasyld0zxr1p79lzf1.jpg" alt="Demo application screenshot" width="800" height="400"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Disclaimer:&lt;/strong&gt; I work at Synergy Codes, the team behind Workflow Builder, and this article was first published on the &lt;a href="https://www.workflowbuilder.io/blog/data-driven-workflow-editor" rel="noopener noreferrer"&gt;Workflow Builder blog&lt;/a&gt;. The demo and the code are mine.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; The editor in Workflow Builder is data-driven. A backend serves the node palette, the property panels, and the theme as JSON and CSS variables, so you customize the editor by editing data, not by rewriting code. I built a demo with two editors that share every line of code yet look and behave like different products. &lt;a href="https://dominikapacholec.github.io/WB-data-driven-demo/" rel="noopener noreferrer"&gt;Live demo&lt;/a&gt; · &lt;a href="https://github.com/dominikapacholec/WB-data-driven-demo" rel="noopener noreferrer"&gt;source&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;New to Workflow Builder? It is an open-source framework for workflow orchestration you embed in your product; this post is about its visual editor. The editor in &lt;a href="https://www.workflowbuilder.io" rel="noopener noreferrer"&gt;Workflow Builder&lt;/a&gt; is data-driven. A backend serves the node palette, the property panels, and the theme as JSON and CSS variables. So you customize the editor by editing data, not by rewriting code. The real win is flexibility: one editor can serve many use cases, clients, and brands. You can &lt;a href="https://dominikapacholec.github.io/WB-data-driven-demo/" rel="noopener noreferrer"&gt;try the demo live&lt;/a&gt; or read &lt;a href="https://github.com/dominikapacholec/WB-data-driven-demo" rel="noopener noreferrer"&gt;the source&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fauniencga1royugdcfnc.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fauniencga1royugdcfnc.gif" alt="Switching the profile dropdown changes the whole editor – palette, node shapes, panel fields, navigation, tagline, and theme – because it is all input data." width="719" height="341"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Switching the profile reloads a different configuration and the editor reshapes itself: palette, node shapes, panel fields, navigation, tagline, font, radii, and color mode. Nothing in the code changed, only the data did.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  What "data-driven" means for a workflow editor
&lt;/h2&gt;

&lt;p&gt;Workflow Builder is an open-source framework for workflow orchestration in your product. Its editor SDK, the part this post is about, puts a visual workflow editor inside your own React app. Data-driven means its configurable surfaces are data, not code. You would normally hard-code these parts. Here they are just data the editor loads when it opens: the node palette, the property panels, and the theme. The code that draws them stays the same.&lt;/p&gt;

&lt;p&gt;To see how far it went, I built two editors that share every line of code. One is an invoice approval tool, teal and calm, top-down, light mode. The other is an AI content pipeline, amber and sharp, left-to-right, dark mode. When I switched between them, the palette, the panels, the seeded diagram, and the whole look changed. My source tree did not.&lt;/p&gt;

&lt;p&gt;What I liked most was how easy that was. The hard part, a working editor, was already there. I only had to touch the data.&lt;/p&gt;
&lt;h2&gt;
  
  
  Getting the configuration from a server, not the bundle
&lt;/h2&gt;

&lt;p&gt;I gave myself one rule: the configuration had to arrive over the network, the way it would from a real backend. Nothing gets imported from the config folder, and nothing sits in &lt;code&gt;public/&lt;/code&gt;. A small Vite middleware plays the part of the backend and serves each profile as JSON:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;GET /api/profiles.json           -&amp;gt; the switcher menu
GET /api/profiles/:id.json       -&amp;gt; the four files, assembled into one document
GET /api/profiles/:id/:part.json -&amp;gt; a single file (feeds the in-app editor)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The routes end in &lt;code&gt;.json&lt;/code&gt; on purpose. The build can freeze them into static files, so a plain static host answers the exact same requests. The editor cannot tell a live backend from a folder of files.&lt;/p&gt;

&lt;p&gt;You can watch the configuration land in the browser's Network tab. A profile is just JSON: a palette, a theme, a seeded diagram, and the chrome around them. The app fetches it and hands it to the editor as it loads. Point the same code at a real API, and nothing else changes. The editor already treats its own configuration as remote data.&lt;/p&gt;

&lt;p&gt;So the config comes over HTTP, from a mock backend. But how much of the editor can it actually describe?&lt;/p&gt;

&lt;h2&gt;
  
  
  The palette is a list, not code
&lt;/h2&gt;

&lt;p&gt;The palette is the clearest case. It is a list you hand to the editor, so instead of registering node types in React, you describe them in JSON. Here is one node from that config:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json-doc"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"ai.analyze"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"label"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Analyze Invoice"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"icon"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Robot"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"properties"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;"model"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"string"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"label"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Model"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"options"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
        &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"label"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Claude Opus 5"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"claude-opus-5"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"icon"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"ClaudeLogo"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"label"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Claude Sonnet 5"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"claude-sonnet-5"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"icon"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"ClaudeLogo"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
        &lt;span class="c1"&gt;// … more options&lt;/span&gt;
      &lt;span class="p"&gt;]&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"prompt"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"string"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"label"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Prompt"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"placeholder"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"…"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="c1"&gt;// … timeoutSeconds&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"required"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"model"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"prompt"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"ui"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;"preset"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"general"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"elements"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
      &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Accordion"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="nl"&gt;"label"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Model"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="nl"&gt;"elements"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
          &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Select"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"scope"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"#/properties/model"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
          &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"VariableTextArea"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"scope"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"#/properties/prompt"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
        &lt;span class="p"&gt;]&lt;/span&gt;
      &lt;span class="p"&gt;}&lt;/span&gt;
      &lt;span class="c1"&gt;// … an "Execution" accordion with the timeout&lt;/span&gt;
    &lt;span class="p"&gt;]&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="c1"&gt;// … defaults, outputSchema&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;One quick warning before you copy this. This short shape is the demo's own. It is not what the SDK reads directly. The app first turns each entry into what the SDK wants: a JSON Schema and a JSON Forms ui schema. So it will not work if you paste it in. And that is the point. You can design your own config format. You just convert it to what the SDK expects afterward. You shape the data to fit your product. The &lt;a href="https://www.workflowbuilder.io/blog/custom-node-types-workflow-builder-complete-guide" rel="noopener noreferrer"&gt;custom node types&lt;/a&gt; guide shows the full node format the SDK expects.&lt;/p&gt;

&lt;p&gt;The content pipeline's palette is a different list: a content brief, a draft node, a quality gate, an editor review.&lt;/p&gt;

&lt;p&gt;The app even has a fingerprint button. Turn it on, and every node points back to the config entry it came from. The canvas is a projection of the data.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftgo5n5s9311af7w1hk5n.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftgo5n5s9311af7w1hk5n.gif" alt="Each node on the canvas is labeled with the configuration entry it was compiled from, including the AI node." width="760" height="390"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;The fingerprint toggle tags every node, including the AI node, with the config entry that produced it.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The palette places the nodes. The panel is where each node earns its properties, and it is the surface I most expected to need code.&lt;/p&gt;
&lt;h2&gt;
  
  
  The property panels are JSON Schema and JSON Forms
&lt;/h2&gt;

&lt;p&gt;The panel is the deepest data surface of all. Each one comes from two structures the profile carries: a JSON Schema that declares the fields and their rules, and a JSON Forms ui schema that declares the layout. No form component here is written by hand, except a few deliberate custom controls I will come back to. It is the one place where config runs out and you drop to code.&lt;/p&gt;

&lt;p&gt;Form validation lives in the schema. On the human-approval node, an &lt;code&gt;allOf&lt;/code&gt; block turns on an extra rule under a condition. When the approval mode is auto, the threshold must be at least 1:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="nl"&gt;"allOf"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
  &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;"if"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;   &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"properties"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"approvalMode"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"const"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"auto"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"then"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"properties"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"thresholdAmount"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"number"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"minimum"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;]&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Because the schema is data, you can tighten a rule while the editor runs. The demo has a Config Studio, a panel that edits the live config. Raise a field's minimum there. Reopen a node that is already on the canvas, and a validation badge appears on it. The diagram never moved. Only the rule it is checked against did.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fizlledupz9zksy6ykcaa.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fizlledupz9zksy6ykcaa.gif" alt="Editing the JSON Schema minimum adds a validation badge to a node already on the canvas, without changing the diagram." width="600" height="308"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Config Studio → Schema: raising thresholdAmount's minimum to 5000, then reopening a node that was already placed. A validation badge appears, and the diagram is untouched.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Layout and conditional visibility sit in the ui schema. Controls fall into accordions and columns, and a &lt;code&gt;rule&lt;/code&gt; shows or hides one based on another field's value. Here the threshold appears only when the reviewer picks auto-approval:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Text"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"scope"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"#/properties/thresholdAmount"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"options"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"customRenderer"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"CurrencyAmount"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"currency"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"EUR"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"rule"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;"effect"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"SHOW"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"condition"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"scope"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"#/properties/approvalMode"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"schema"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"const"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"auto"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The same mechanism does &lt;code&gt;HIDE&lt;/code&gt;, &lt;code&gt;ENABLE&lt;/code&gt;, and &lt;code&gt;DISABLE&lt;/code&gt;. Which fields a reviewer sees, when they are required, whether they can be edited: the profile decides all of it. So you change the form by editing data, not by editing code.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqacix1wenaci41u2a6a6.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqacix1wenaci41u2a6a6.gif" alt="The properties panel shows and hides fields as the approval mode changes, driven entirely by JSON rules." width="720" height="370"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Changing the approval mode shows and hides thresholdAmount, dueAfterHours, and a warning. It is a JSON Forms rule plus allOf, no React.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;This part surprised me the most. I did not have to build the form or style it. For example, to put controls side by side, I just wrote &lt;code&gt;HorizontalLayout&lt;/code&gt; in the data. Normally you do all of this by hand: the node look, the panel styling, the form logic. Here the basic controls come ready. That saved me a lot of time.&lt;/p&gt;

&lt;p&gt;Fields and rules covered behavior. The last surface to move was the look.&lt;/p&gt;
&lt;h2&gt;
  
  
  The look is a set of tokens
&lt;/h2&gt;

&lt;p&gt;The theme is a map of design tokens. They use the SDK's own CSS variable names, split across a base, a light mode, and a dark one. My two profiles differ here by only a few values. Yet they read like products from different companies. The shell and the canvas draw from the same tokens:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json-doc"&gt;&lt;code&gt;&lt;span class="c1"&gt;// Invoice approval – theme.json (light)&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"--wb-ds-colors-acc1-500"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"#0f766e"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"--wb-public-font-family"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"\"Poppins\", sans-serif"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"--wb-public-node-border-radius"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"12px"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"--wb-public-transition"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"160ms"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="c1"&gt;// Content pipeline – theme.json (dark)&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"--wb-ds-colors-acc1-500"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"#d97706"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"--wb-public-font-family"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"\"JetBrains Mono\", monospace"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"--wb-public-node-border-radius"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"0px"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;  &lt;span class="nl"&gt;"--wb-public-transition"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"0s"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Change one brand value and everything repaints together: buttons, node borders, active ports, icons, the task inbox, the timeline. Changing the brand means editing token values, not CSS. A design system, in this setup, is a file you serve rather than a build you ship.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6ranryzsy8as5li9mu3p.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6ranryzsy8as5li9mu3p.gif" alt="A single design-token change recolors the whole editor at once; a Copy theme.json button exports the served config file." width="720" height="370"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Dragging the brand token recolors the whole editor at once. Copy theme.json hands back the exact file a backend would serve.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the data stops
&lt;/h2&gt;

&lt;p&gt;Almost everything is data. The exception is custom rendering: the React that draws a control or a node when the built-in ones are not enough. A node's fields, validation, layout, icon, and built-in shape all come from config. But when a control has to behave in a way JSON Forms cannot express, you write a custom renderer in React, like the currency input on the threshold field. Even then the choice stays in data: a single key, &lt;code&gt;customRenderer&lt;/code&gt;, says which field uses it.&lt;/p&gt;

&lt;p&gt;A few things are code by nature: a custom node or edge, a plugin, and connection validation. Connection validation is the rule for which ports may link on the canvas, not the form validation the schema does. Run-time node behavior is code too: with Temporal, each node type needs an executor function. A new process built from node types that already exist needs no new code, but a new node type needs its executor before it can run.&lt;/p&gt;

&lt;h2&gt;
  
  
  The subject: a human-in-the-loop workflow
&lt;/h2&gt;

&lt;p&gt;The workflow the demo is built around is a &lt;a href="https://www.workflowbuilder.io/blog/human-in-the-loop-ai-agent-workflow-builder" rel="noopener noreferrer"&gt;human-in-the-loop&lt;/a&gt; invoice approval: an automated run reaches a decision, pauses for a person, and continues once they approve. The demo mocks the execution with local state. So the run, the task inbox, and the timeline show the experience, not a real engine. In Workflow Builder, that engine is Temporal: the framework's Temporal plugin &lt;a href="https://www.workflowbuilder.io/blog/live-workflow-execution-visualization" rel="noopener noreferrer"&gt;runs the workflow&lt;/a&gt; and pauses it at the approval step until a person decides.&lt;/p&gt;

&lt;p&gt;Even the routing is a configured value, not a coded one. The branch that sends large invoices to a human is just a condition in the data. Raise its threshold past the mocked amount, and the next run auto-approves. No task is created.&lt;/p&gt;

&lt;p&gt;Here is the business case underneath the demo, and it is the part I find exciting. Because the configuration arrives from a server, a profile is really a tenant. Serve a different profile per customer. Each one gets its own node vocabulary, its own validation, and its own branding, all from data and one deployment. One editor, many tenants, no fork. From one codebase, you can build different views, profiles, or whole product variants. Anyone who can edit the data can extend the app, without touching the code. It is an app each customer &lt;a href="https://www.workflowbuilder.io/blog/the-holy-grail-of-frontend-an-app-you-configure-like-a-car" rel="noopener noreferrer"&gt;configures like a car&lt;/a&gt; rather than one you re-manufacture per account.&lt;/p&gt;

&lt;p&gt;If I had to sum up working with Workflow Builder: get the base right, and the data does the rest.&lt;/p&gt;

&lt;p&gt;Workflow Builder is an open-source framework for workflow orchestration in your product. Its editor SDK, used in this post, is a production-ready React workflow editor built on React Flow, with a schema-driven properties panel, plugin architecture, and JSON serialization. The framework also includes a Temporal plugin that runs the diagrams your users draw as durable workflows, and an execution backend that starts runs and streams each step to your app. You can use the whole stack or only the editor: it saves workflows as JSON, so you can also run them on an engine you already have. The Community Edition (open source, Apache 2.0) contains all of these parts, and the Enterprise Edition adds advanced canvas plugins, such as auto-layout and edge routing. Everything in this post uses the free Community Edition.&lt;/p&gt;

</description>
      <category>react</category>
      <category>webdev</category>
      <category>javascript</category>
      <category>opensource</category>
    </item>
    <item>
      <title>From React Flow to Workflow Builder: what you keep, and what you gain</title>
      <dc:creator>Dominika Pacholec</dc:creator>
      <pubDate>Thu, 16 Jul 2026 09:35:23 +0000</pubDate>
      <link>https://dev.to/workflowbuilder/from-react-flow-to-workflow-builder-what-you-keep-and-what-you-gain-4b9m</link>
      <guid>https://dev.to/workflowbuilder/from-react-flow-to-workflow-builder-what-you-keep-and-what-you-gain-4b9m</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Foz80vta1dza374z4u48c.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Foz80vta1dza374z4u48c.jpg" alt=" " width="800" height="400"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; I've spent 7+ years building diagram-heavy and node-based UIs, so when I dug into Workflow Builder – our SDK at Synergy Codes – I went to the public source to see what it actually does to a React Flow app. Short version: it's a superset, not a replacement. React Flow stays underneath as a peer dependency, and your React Flow knowledge carries over. Where the work is: graph state moves into the SDK's store, and custom nodes get rewritten as node templates. This is an honest breakdown of what stays, what changes, and what you gain – every claim checked against the public source. If you're a React Flow dev weighing build-vs-buy for a workflow editor, this one's for you.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Disclaimer:&lt;/strong&gt; I'm a frontend engineer at Synergy Codes, the company behind Workflow Builder. I build diagram and node-based UIs for a living, but I'm not on the Workflow Builder SDK team – I went through the public repo and docs to write this, and kept it honest, including the parts that cost you effort.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published on the &lt;a href="https://www.workflowbuilder.io/blog/from-react-flow-to-workflow-builder" rel="noopener noreferrer"&gt;Workflow Builder blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;A production workflow editor on React Flow isn't one feature – it's a properties panel, undo/redo, a palette, persistence, layout, validation. Workflow Builder gives you that whole layer while keeping React Flow underneath.&lt;/p&gt;

&lt;h2&gt;
  
  
  Can you still do everything you did in React Flow?
&lt;/h2&gt;

&lt;p&gt;Yes. Almost everything you reach for in a React Flow editor works the same way inside Workflow Builder, because React Flow is still doing the work. Here is how the common building blocks map across:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What you do in React Flow&lt;/th&gt;
&lt;th&gt;Status&lt;/th&gt;
&lt;th&gt;In Workflow Builder&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Render custom nodes&lt;/td&gt;
&lt;td&gt;This changes&lt;/td&gt;
&lt;td&gt;Start from 7 built-in node templates (trigger, action, conditional, decision, delay, notification, AI agent), or write your own as a node template with a schema for its data&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Build custom edges (&lt;code&gt;EdgeProps&lt;/code&gt;)&lt;/td&gt;
&lt;td&gt;Same as React Flow&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;EdgeProps&lt;/code&gt; straight from React Flow, plus ready components like labeled and self-connecting edges&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Configure the canvas and handle events (zoom, pan, fit view, &lt;code&gt;onNodeClick&lt;/code&gt;, &lt;code&gt;onPaneClick&lt;/code&gt;)&lt;/td&gt;
&lt;td&gt;Same as React Flow&lt;/td&gt;
&lt;td&gt;Props pass straight through to the underlying &lt;code&gt;&amp;lt;ReactFlow&amp;gt;&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Manage graph state (read and update)&lt;/td&gt;
&lt;td&gt;This changes&lt;/td&gt;
&lt;td&gt;Workflow Builder sits above React Flow and owns its state – the SDK store is the source of truth, and you read and update the graph through it. React Flow's hooks (&lt;code&gt;useReactFlow&lt;/code&gt;, &lt;code&gt;useNodes&lt;/code&gt;) stay available for reading and inspecting the live canvas&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Build the core editor layer yourself&lt;/td&gt;
&lt;td&gt;New in WB&lt;/td&gt;
&lt;td&gt;A node library, a schema-driven properties panel, a drag-and-drop palette, read-only mode, and typed persistence (localStorage, REST, or callback)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Wire up editor basics yourself&lt;/td&gt;
&lt;td&gt;New in WB&lt;/td&gt;
&lt;td&gt;Undo / redo and copy / paste ship as free, open plugins on the public plugin API&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Graph state is the one area that works differently. Workflow Builder runs React Flow in controlled mode and owns the graph in its own store, so the store is the source of truth: you read and update the graph through the SDK's actions. React Flow's hooks still return the live canvas state for reads and inspection, but the store – not direct &lt;code&gt;nodes&lt;/code&gt; / &lt;code&gt;edges&lt;/code&gt; mutation – is how you drive changes. Keeping state in a dedicated store is also a performance choice: it follows the patterns Synergy Codes' &lt;a href="https://www.synergycodes.com/webbook/guide-to-optimize-react-flow-project-performance" rel="noopener noreferrer"&gt;guide to optimizing React Flow performance&lt;/a&gt; recommends for keeping larger graphs responsive.&lt;/p&gt;

&lt;p&gt;Everything else passes through. You hand React Flow props to Workflow Builder, and they land on the underlying canvas untouched. When you build nodes, edges, or plugins, you still import &lt;code&gt;Handle&lt;/code&gt;, &lt;code&gt;Position&lt;/code&gt;, and &lt;code&gt;EdgeProps&lt;/code&gt; from &lt;code&gt;@xyflow/react&lt;/code&gt; – same package, same docs, same upgrade path. And when you need the raw canvas API for something the SDK does not surface, it is still reachable.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you gain on top
&lt;/h2&gt;

&lt;p&gt;Workflow Builder adds the layer React Flow deliberately leaves to you – the part that turns a working canvas into a product. React Flow gives you a fast, flexible renderer. It does not give you a properties panel, history, or a palette, because those are application concerns. That is precisely the layer you would build by hand, and it is what Workflow Builder ships ready.&lt;/p&gt;

&lt;p&gt;The table above lists what that layer includes. What a list cannot show is why each piece is worth having ready – most of it is work that looks small and turns out not to be:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;A node library&lt;/strong&gt; – the built-in node types (trigger, action, conditional, decision, delay, notification, AI agent) mean you are not modeling and styling the common workflow primitives from zero. You extend or replace them instead of inventing them.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A schema-driven properties panel&lt;/strong&gt; – one schema drives the form, its validation, and the node's data shape, so they stay in sync as nodes evolve instead of drifting apart across three hand-maintained places.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Undo / redo&lt;/strong&gt; – history is one of those features that looks simple and rarely is. You get a working implementation, built on a public change-tracking primitive, to keep as-is, swap for your own model, or drop.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A node palette&lt;/strong&gt; – a ready drag-and-drop panel for adding nodes to the canvas, already connected to the store so dropped nodes land in the graph correctly.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Read-only mode&lt;/strong&gt; – locking the canvas for viewers while keeping full inspection is state you would otherwise thread through every interaction by hand.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A typed workflow document&lt;/strong&gt; – instead of persisting loose JSON and hoping it loads back correctly, the graph has one canonical, typed shape, older formats are migrated forward, and saving to localStorage, a REST endpoint, or a callback is a thin adapter on top.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;React Flow renders a canvas but leaves the surrounding UI to you. Workflow Builder ships the same component library and design system it is built on, so the editor and the controls around it share one consistent look out of the box. It is fully tokenized, with theming and white-label support, so you can override tokens to make the editor match the app it is embedded in. That is polish React Flow leaves entirely to you.&lt;/p&gt;

&lt;p&gt;The layer is &lt;strong&gt;plugin-first&lt;/strong&gt;: optional features register through a public plugin API and can be added or removed without breaking the editor. The same plugin surface that builds the reference undo / redo also lets you add toolbar buttons, inject UI into known slots, and ship your own translations.&lt;/p&gt;

&lt;p&gt;This is not theoretical. The demo app ships two full, open plugins built on the public plugin API – &lt;a href="https://github.com/synergycodes/workflowbuilder/tree/main/apps/demo/src/app/plugins" rel="noopener noreferrer"&gt;copy / paste and undo / redo&lt;/a&gt; – which prove the plugin API works and show the pattern you'd follow for your own. Heavier diagram operations – smart edge routing and node avoidance, edge reshaping, ELK auto-layout, and PDF export – are Enterprise features delivered through Overflow, and the other folders in the demo are placeholders.&lt;/p&gt;

&lt;p&gt;Some of the heavier features sit in the Enterprise Edition, and it is worth being clear about the line. The open SDK exposes layout-direction control and fit-view helpers. Production-grade &lt;strong&gt;ELK auto-layout&lt;/strong&gt;, &lt;strong&gt;smart edge routing&lt;/strong&gt;, on-canvas &lt;strong&gt;edge reshaping&lt;/strong&gt;, &lt;strong&gt;PDF export&lt;/strong&gt;, and an in-browser &lt;strong&gt;flow runner&lt;/strong&gt; are delivered through Overflow in the &lt;a href="https://www.workflowbuilder.io/blog/edge-routing-in-workflow-editors-technical-deep-dive" rel="noopener noreferrer"&gt;Enterprise Edition&lt;/a&gt;. Either way, React Flow stays the renderer underneath – these features layer on top, they do not replace it.&lt;/p&gt;

&lt;p&gt;So the trade is the opposite of the one developers fear. You keep React Flow's full range, and you add the editor features that are surprisingly hard to build well. If something is possible in React Flow, it is possible in a Workflow Builder editor – plus a great deal you would otherwise build yourself.&lt;/p&gt;

&lt;h2&gt;
  
  
  When does moving from React Flow to Workflow Builder make sense?
&lt;/h2&gt;

&lt;p&gt;A React Flow prototype that works eventually has to &lt;a href="https://www.workflowbuilder.io/blog/from-react-flow-templates-to-production-when-a-workflow-editor-becomes-a-real-product-feature" rel="noopener noreferrer"&gt;become a product&lt;/a&gt; – and that is when the properties panel, undo / redo, palette, and persistence stop being nice-to-haves. The choice at that point is whether to build the editor layer around React Flow yourself or start from one that already exists.&lt;/p&gt;

&lt;p&gt;Adopting Workflow Builder does not mean rebuilding the canvas. It does mean changing where two things live. You mount &lt;code&gt;&amp;lt;WorkflowBuilder.Root&amp;gt;&lt;/code&gt; instead of rendering &lt;code&gt;&amp;lt;ReactFlow&amp;gt;&lt;/code&gt; yourself, and graph state moves into the SDK store. Your edge components carry over unchanged. Your custom nodes are rewritten as node templates, with their data described as a schema – that is the real migration work, and it is honest to call it work. What transfers is your React Flow knowledge; what changes is where the nodes and state live.&lt;/p&gt;

&lt;p&gt;Because the SDK sits on React Flow instead of forking it, you are not locked in. React Flow stays underneath, the raw canvas stays reachable, and you keep its API and upgrade path. Backing out still means unwinding the node and state changes you made, but you are building on the library you already know, not a fork you would have to escape.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.workflowbuilder.io/" rel="noopener noreferrer"&gt;Workflow Builder&lt;/a&gt; is a production-ready React SDK for embedding visual workflow editors, built by Synergy Codes on top of React Flow. It ships as Community Edition (open source, Apache 2.0) and Enterprise Edition, and the team spent the &lt;a href="https://www.workflowbuilder.io/blog/build-vs-buy-workflow-editor-hidden-cost-react-flow" rel="noopener noreferrer"&gt;14–25 weeks of canvas work&lt;/a&gt; so you can start from the layer above. If you are weighing a React Flow workflow editor against building one from scratch, that head start is the whole point.&lt;/p&gt;

&lt;p&gt;The open-source Community Edition is a solid start on its own, and enough to ship many editors. If you are building something more complex, Synergy Codes also runs &lt;a href="https://www.workflowbuilder.io/consulting" rel="noopener noreferrer"&gt;discovery workshops&lt;/a&gt; to shape the product with your team – optional help, not a prerequisite for using the SDK.&lt;/p&gt;

</description>
      <category>react</category>
      <category>reactflow</category>
      <category>webdev</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
