Open-Source Workflow Components for JavaScript Applications
Build visual workflow builders, editors and execution engines using modular JavaScript components.
NoCode JS is a collection of framework-agnostic libraries for building workflow tools, automation platforms and no-code products. The ecosystem includes a visual workflow designer, a declarative editor generator and a workflow execution engine.
Works with React, Angular, Svelte and vanilla JavaScript.
NoCode JS provides three independent workflow components that can be used separately or combined into a complete workflow platform.
Workflow Designer
Visual workflow builder.
Workflow Editor
Declarative configuration editor.
Workflow Machine
Workflow execution engine.
All components share the same workflow definition model, which makes it easier to design, configure and execute workflows consistently.
Workflow Builder Components
NoCode JS provides modular workflow components for building visual workflow tools.
Instead of implementing a workflow system from scratch, you can combine three independent JavaScript components: Workflow Designer, Workflow Editor and Workflow Machine.
All components share the same workflow definition model and can be used together or independently.
Sequential Workflow Designer
Visual workflow builder for web applications.
The Designer is a framework-agnostic JavaScript component that allows users to create workflows using a visual canvas.
It provides a drag-and-drop interface where processes are defined as sequential steps and stored as JSON workflow definitions.
Developers can fully customize the UI, step types and behavior to match their own product.
Typical use cases include automation builders, AI workflow editors and internal workflow tools.
Declarative configuration editor for workflow steps.
The Editor generates UI editors and validation logic from a workflow definition model.
Instead of manually implementing configuration forms for each step, developers define a schema which is used to automatically generate the editing interface and validation rules.
The same model can be used both in the frontend and backend, ensuring that workflow definitions remain consistent and valid across the entire system.
The Machine executes workflow definitions created with the Designer and validated by the Editor.
It processes workflow steps sequentially and can run in both frontend and backend environments.
Developers implement step handlers that define how each step behaves during execution, allowing workflows to integrate with external APIs, services or business logic.