Summary

Workflow Builder is an Apache 2.0 React SDK designed for embedding visual drag-and-drop workflow editors into digital products. It targets developers building B2B SaaS, AI agent platforms, and automation tools, offering a flexible, back-end-agnostic solution with a swappable execution engine, proven with Temporal, to streamline the integration of complex workflow functionalities.

How It Works

The system leverages React Flow for its visual editor and Temporal for robust workflow execution. Its core design emphasizes a plugin-first architecture, allowing optional features to be added or removed without impacting the core application. This modularity extends to a swappable back-end and execution engine, enabling integration with diverse infrastructure while providing a reference stack for AI workflows.

Quick Start & Requirements

• Installation: Embed SDK via npm (@workflowbuilder/sdk), run demo (pnpm dev:demo), or deploy full stack (pnpm setup:env, pnpm infra:up, pnpm dev:ai-studio).
• Prerequisites: Node.js (v22.12.0), pnpm (v10.9.0), Docker Desktop (for full stack).
• Setup Time: ~1 min (SDK), ~2 min (Demo), ~10 min (Full Stack).
• Links: Live Demo, Documentation, npm.

Highlighted Details

• Plugin-first architecture allows for highly customizable and extensible feature sets.
• Schema-driven properties panels enable declarative configuration of node inputs.
• Workflows are JSON-serializable, facilitating integration with any backend.
• Includes a Design System Kit for theming and white-labeling.
• Offers various plugins like ELK Layout, Undo/Redo, Copy/Paste, and PDF export.

Maintenance & Community

• Active community support via Discord.
• Used in production by companies like Vercom, Athena Intelligence, and Plura AI.

Licensing & Compatibility

• License: Apache 2.0 (Community Edition). An Enterprise Edition with commercial licensing is available.
• Compatibility: Apache 2.0 is permissive for commercial use and integration into closed-source products.

Limitations & Caveats

The included reference backend and execution worker are explicitly for local development only. They lack essential production security features such as authentication, authorization, and tenant isolation, making them unsuitable for deployment without significant security enhancements.