Glossary

The HiveFlow ontology in one page. Each term includes its relations to other terms, so the whole domain reads as one consistent graph.

Core execution model

• Workflow (Flow) — an automated process defined as a graph of nodes and edges, executed by HiveFlow. Contains nodes; connected by edges; started by a trigger; produces outputs. → What is a workflow?
• Node — one step of a workflow, of a specific type from the catalog (44 types, 8 categories). Belongs to a flow; receives/emits data through edges; configured via its edit modal.
• Edge (Connection) — a directed link between two nodes through which data flows. Edges into an LLM Agent make the source node a tool of that agent.
• Canvas — the visual editor where flows are built. Renders nodes and edges; offers versioning, sharing, export/import. → Building flows
• Trigger — whatever starts an execution: manual run, chat/form message, webhook, WhatsApp, extension, schedule or API call. → Running flows
• Execution (Run) — one pass of data through a flow. Observable per node via its Console; aggregated in Analytics; consumes credits when LLM nodes run.
• Variable — a {{node_id.field}} reference that injects an upstream node's output into a downstream node's configuration.
• State / Memory — data that outlives a step: session context in chats, the Memory node for run-scoped storage, and databases for persistence.

Intelligence layer

• LLM Agent (node) — the node that runs a language model with a role, objective, prompt and optional tools. The intelligent step of a workflow. → The LLM Agent node
• Agent — a flow with the conversational pattern (chat_input → llm → chat_output) presented with a chat UI, sessions, tasks and reminders. Is a workflow. → What is an AI agent?
• Genius — HiveFlow's built-in assistant: an agent with tools over the platform itself; it creates and runs flows, apps and tools from chat. → Using Genius
• Skill — a Markdown knowledge block injected as context into AI surfaces (Genius, agents/flows, flow generator, app builder) according to its scope. Knowledge, not actions. → Skills
• Function calling — the mechanism by which an LLM decides to invoke tools during a run, possibly over multiple rounds. Connects the intelligence layer to tools. → Adding tools
• Session — one conversation with an agent or public chat, holding its message history and context window.

Tools and integrations

• Tool — any capability an agent can call. Two kinds in HiveFlow: MCP tools (from integrations) and Hive App tools (from App Instances).
• Integration — an external service (database, SaaS, cloud) connected with credentials or OAuth. Registers an MCP server owned by your account. → Connecting integrations
• MCP (Model Context Protocol) — the open standard HiveFlow uses for tools, in both directions: consuming external MCP servers and exposing flows as MCP servers. → MCP nodes
• App Instance (Tool) — a built-in structured mini-app: Kanban, CRM, Inventory, Analytics or Chat. Readable/writable by agents via the hiveapp node. → Tools

Product layer

• Hive App — an AI-generated web app (files, framework, versions) that can be deployed publicly and linked to a flow as its backend. → Creating Hive Apps
• I/O contract — the typed description of what a Hive App sends to its linked flow and what it gets back. → Connecting apps and flows
• Template — a reusable flow published to be cloned, from the Templates section or the community Marketplace.
• Deployment — publishing a Hive App (draft → preview → deployed) or activating a flow's public surfaces.

Platform layer

• Organization — the collaboration unit: members, roles, permissions and billing. Contains workspaces.
• Workspace — a scoped space inside an organization holding flows, apps, skills and integrations.
• Credits — the usage currency: every LLM call (flows, agents, Genius, app builder) consumes credits from the balance.
• API key — a server-to-server credential for the HiveFlow API; trigger nodes carry their own per-flow keys.