Platform and projects
FlowX.AI Designer: The web app where you build everything: processes, workflows, UIs, data sources, and AI agents. See the FlowX.AI Designer overview. Project: The container that groups all resources and dependencies needed to implement a use case: processes, workflows, UI, enumerations, media, and integrations. See Projects. Library: A specialized project that serves as a reusable container for resources shared across multiple projects. See Libraries. Workspace: A logically isolated business context within one FlowX instance. An organization can run multiple workspaces, each with its own projects and access rights. See Workspaces. Dependency: A link from a project to a library version, making that library’s resources available in the project. See Dependencies. Version: A tracked snapshot of a project’s configuration. Projects evolve through submitted versions, which are then packaged into builds. See Versioning. Build: A deployable package of a project that encapsulates all its resources into a single unit. Builds are what run in an environment. See Builds. Active policy: The strategy that selects which build of a project is active in a runtime environment. See Active policy. Configuration parameters overrides: Environment-specific values for parameters within a project, so the same build can behave differently per environment. See Configuration parameters overrides. Config-time vs runtime: Config-time is where you design (Designer, projects, versions); runtime is where builds execute and end users interact with running instances.Processes (BPMN)
Process definition: The blueprint of a business process: a graph of nodes linked by sequences, modeled in BPMN. See Process definition. Process instance: One specific execution of a process definition, carrying its own data and state. Instances can be executed, monitored, and optimized. See Process instance. Node: A visual representation of a point in your process: where a record enters, transitions, or exits. Node types include user tasks, service tasks, and message events. See Process nodes. Token: The current position in the process flow. A token moves through the node graph as the instance advances; parallel paths mean multiple tokens. See Token. Node action: An activity a node handles, such as saving data, calling a business rule, or communicating with plugins and integrations. See Node actions. Business rule: An action type that configures a script on a BPMN node to express business logic or decision-making within a process. See Business rule action. Subprocess: A process started from within another process, used to reuse and compose flows. See Subprocess.Workflows and integrations
Workflow: An integration flow built in the Integration Designer, used for data processing, transformation, and AI operations across connected systems. Not a BPMN process: workflows are started from processes or triggers, and their nodes are grouped into Flow Control, Data Operations, Tools, and AI categories (AI Text, AI Document, AI Image, and AI Data Operations, plus AI Agents). See Integration Designer. Integration Designer: The drag-and-drop workspace for connecting FlowX to external systems via REST APIs, and for building workflows. See Integration Designer. Data source: A configured connection a workflow or process can use. Types include RESTful System, FlowX Database, MCP Server, Email Trigger, Email Sender, Knowledge Base, Microsoft Outlook, and Incoming Webhook. FlowX Database: A built-in data source for storing and accessing structured data across processes and apps, without standing up an external database. See FlowX Database. Knowledge Base: A managed store of documents and dynamic data that gives AI agents contextual information for retrieval-augmented generation. See Knowledge Base integration. Incoming Webhook: A data source that starts or advances flows when an external system sends an HTTP POST, secured with API keys. See Incoming Webhooks. Email Trigger: A data source that monitors an IMAP mailbox and starts process instances when emails arrive. See Email Trigger.User interfaces
UI Designer: The visual, multi-platform tool for designing interfaces that render on web, iOS, and Android without extensive coding. See UI Designer. UI Flow: A reusable, multi-platform user interface that runs without the overhead of a BPMN process. See UI Flows. UI Flow session: One user’s active interaction with a UI Flow, with its own status, audit trail, and associated processes. See UI Flow Sessions. Custom component: A React component you build and register to extend the built-in UI component palette, with access to process data and actions. See Custom components.AI Platform
Config-time agents: AI agents built into the FlowX Designer that help you build faster: AI Analyst, AI Designer, AI Developer, and AI Assistant. See Config-time agents. Business agents: AI agents that power experiences for end users in your apps, created with the Agent Builder. See AI in FlowX. Agent Builder: The no-code/low-code tool for creating custom AI agents. See Agent Builder. Chat-driven workflow: A workflow behind a multi-turn chat experience, with session memory, intent routing, and context-aware responses. See Chat-driven workflows.Deployment and releases
SaaS: FlowX operated as a managed cloud service. New feature releases reach SaaS first. Self-hosted: FlowX deployed and operated in your own infrastructure. Self-hosted deployments follow LTS releases. LTS release: A long-term-support platform version (such as 5.9.x) that receives maintenance patches and is the basis for self-hosted deployments. Feature release: A monthly release between LTS versions that ships new capabilities to SaaS; those capabilities reach self-hosted with the next LTS.Related resources
Build your first process
Put the vocabulary to work in a hands-on tutorial.
Cookbooks
Tutorials, guides, and reusable patterns for building on FlowX.AI.