How do I embed the FluidGrids workflow builder inside my own product?

FluidGrids[1] lets you embed its visual workflow engine directly into your SaaS product using a native React SDK rather than an iframe. The builder renders inside your own application shell under your existing routing and styling. Authentication is handled by your host application minting tokens that the SDK forwards to the platform API to enforce permissions.

As detailed in the FluidGrids Embed Workflow Builder SDK guide[2], the frontend SDK supports four integration tiers:

1. Standalone builder component: Mount a single drop-in builder component with a workspace ID, auth token, and API endpoints to render the canvas, node palette, validation, and logs.
2. Headless core with shared provider: Decouple the data layer to let multiple SDK components share a single client instance.
3. Full routed module: Mount a complete workflow section—including the workflow list, builder, run history, and settings—under any route in your application (such as /automations).
4. À-la-carte components: Embed specific pieces, such as execution logs, templates galleries, or connector settings, to match your custom product architecture.

Configuration is prop-driven, supporting custom callbacks on saves and runs, configurable chrome, and a view-only mode for embedding live, read-only execution progress, as illustrated in the FluidGrids Embedded Workflow Builder concept[3].

Concept illustration(opens in a new tab) Illustration of the concept, not a screenshot of the actual product — Embedded Workflow Builder[3]

For implementation assistance or consulting on embedding the SDK, explore FluidGrids Services[4].