Workflow Builder is a frontend SDK for building visual workflow editors inside your own product. It lets you embed a drag-and-drop workflow designer into your SaaS while keeping execution, pricing, and business logic fully in your backend.

Workflow Builder is a white-label SDK, not a standalone SaaS product. You receive source code that becomes part of your application and can be customized to your domain.

Yes. Workflow Builder can serve as a production-ready foundation when building a new product or standalone application where workflows are a core part of the user experience.
‍
Teams use it to avoid reinventing workflow UI from scratch, while still owning execution logic, domain rules, data models, and overall product architecture from day one.

Workflow Builder is not a full workflow orchestration engine. Execution typically happens in your own backend. However, the Enterprise edition includes a Flow Runner plugin that can traverse the workflow graph and execute node functions directly in the editor. This allows teams to preview and test workflow logic before connecting it to their production backend.

n8n, Make, and Zapier are SaaS platforms, a hosted execution for running workflows as a service. Workflow Builder is a SDK designed for team that need an embedded workflow editor to build their own automation or AI-powered products.

Workflow Builder is for:
- SaaS companies embedding workflows into their products
- AI and automation products building agent designers, pipelines, or decision flows
- Engineering teams that already own (or plan to build) workflow execution on their backend

It is not for end users looking for a ready automation tool.

Yes - within boundaries you define. Business users visually connect predefined steps, while developers control available nodes, rules, and validations.

Most teams can build a basic editor, but UX edge cases, performance optimization, state management, and advanced features like multi-user collaboration quickly become complex. These challenges typically take 2–3× longer than expected to solve in a production-ready way. Workflow Builder provides a proven, scalable foundation so your team can focus on business logic instead of rebuilding workflow UX from scratch.

Most teams integrate Workflow Builder in weeks, not months, depending on customization and backend readiness. In fact, some customers have had a fully live workflow editor running within 24 hours of purchase - this is how quickly it can accelerate your product development.

You receive:
- full frontend source code
- configurable node library
- schema-driven properties panel
- plugin architecture
- design system and theming
- advanced features
- support and warranty period
- commercial usage rights

Workflow Builder provides:
- visual workflow canvas
- node & edge modeling
- schema-driven configuration UI
- serialization to JSON
- flow runner
‍
It does not provide back-end execution or orchestration.

You build:
- execution engine
- scheduling and retries
- billing and limits
- permissions logic
- AI calls and integrations

Workflows are represented as JSON. The JSON contains nodes, connections, metadata, and configuration values.

Yes. Because workflows are JSON, you can generate, modify, and version them programmatically via your APIs.

Custom nodes are implemented as React components and configured via JSON schema. You control behavior, forms, validation, and data mapping.

It's fully white-label SDK, so you can adjust:
- colors, typography, layout
- dark / light mode
- node visuals
- panels & controls

Workflow Builder once embedded can look and feel like your branded product.

Common patterns include:
- draft vs production environments
- workflow locking
- role-based permissions
- backend validation before execution

Yes. Teams use Workflow Builder to design agent pipelines, prompt chains, decision trees, and tool-calling flows.

Workflow Builder is available under two licensing models:

- Community Edition – open source under the Apache 2.0 license, which allows commercial use.
- Enterprise Edition – a commercial license that includes additional features, long-term support, and access to consulting services.

Both the Community and Enterprise editions can be used in commercial products. This allows teams to start with the open-source edition and upgrade when their product requires advanced capabilities or enterprise support.

Yes. You may embed and resell Workflow Builder as part of your product.

Yes. You receive the frontend source code. You can modify it, extend it, and maintain it as part of your product.

Workflow Builder is available in two editions:
- Community Edition - open source, licensed under Apache 2.0
- Enterprise Edition - commercial, proprietary version designed for teams that need advanced features, scalability, and long-term support.

The Enterprise Edition of Workflow Builder is typically licensed as a one-time fee. The Community Edition is free of charge and available under the Apache 2.0 license.

No built-in limits. You control usage, execution frequency, billing, and limits in your backend.

No. There is no revenue sharing - monetization is fully controlled by you.

Yes. Many teams start with a limited node set and expand functionality over time.

Yes. While Workflow Builder can be integrated by your own team, many companies choose to work with the Workflow Builder team during the design and implementation phase. Building workflow interfaces involves many UX and architecture decisions that teams often only discover late in development. Our team has over a decade of experience designing diagram-based and workflow products and can help you avoid those pitfalls early.

As one client put it: “We didn’t have experience building this type of interface, and the first conversations with the Workflow Builder team made us realize that. Questions came up that we probably would have only discovered later during development. It clearly showed how important experience and know-how in this area is. Adam Lewkowicz CTO at MessageFlow”
‍
Consulting typically helps teams accelerate design decisions, adapt Workflow Builder to their product faster, and reduce implementation risk.

No. Most teams integrate Workflow Builder independently using the provided source code and documentation. Consulting is optional and typically used to accelerate delivery or reduce risk.

Yes. This is the most common approach. Many teams begin with self-integration and involve us later for specific challenges or refinements.

Yes. We provide end-to-end consulting, including execution engines and backend workflow logic. While Workflow Builder itself focuses on the workflow editor UI, our consulting team can design and implement execution layers, orchestration logic, integrations, and production-ready backend architectures tailored to your product.

No. Our consulting is engagement-based and optional. There is no requirement for ongoing services or retainers.

Teams usually request support, when:
- frontend capacity is limited
- workflows are core to the product UX
- timelines are aggressive
- advanced customization is required

Yes. However, Enterprise customers typically use consulting more frequently due to production scale and commercial requirements.

Consulting is scoped individually based on your needs and timeline. There is no fixed package — you only pay for the support you actually need.