Core Concepts
FluidGrids is built around a small set of objects. The user guides describe the screens; these pages describe what the screens operate on.
| Concept | One line | Page |
|---|---|---|
| Workflow | A graph of nodes under a stable key, stored as immutable versions; one version can be Active. | Understanding Workflows |
| Visual Builder | The canvas that edits a workflow version: nodes, edges, handles, mappings, validation. | Visual Workflow Builder |
| Node | One step. Trigger nodes, built-in nodes, and store nodes. | Understanding Nodes |
| Run | One execution of one version, with per-node state, logs, and typed errors. | Understanding Workflows |
| Connection | A stored, authorised link to an external service used by store nodes. | Integrations |
| Template | A workflow copied as a starting point — from your workspace or the Store. | Workflow Templates |
| AI | LLM nodes, the AI Agent with tools, structured parsing, and the FluidGrids AI assistant. | AI Capabilities |
The workspace boundary
Everything above belongs to exactly one workspace. Workflows, runs, connections, versions, quotas, and roles do not cross workspaces. Sharing a workflow to another workspace is a copy, never a link. This is what lets FluidGrids inherit multi-tenancy, permissions, billing, and audit from Burdenoff Workspaces without any FluidGrids-specific configuration.
Environments
| Environment | App |
|---|---|
| Production (default) | https://app.fluidgrids.ai |
| Alpha (Burdenoff staff only) | https://alphaapp.fluidgrids.ai |
Developer tools point at the GraphQL gateways of the environment. The CLI, Node SDK and MCP server read FLUIDGRIDS_WORKSPACE_ENDPOINT and FLUIDGRIDS_GLOBAL_ENDPOINT, and default to production. See For Developers.