Understand Inflowenger, part by part
Inflowenger is a runtime whose logic is a workflow graph — a substrate for building AI agent orchestrators, autonomous operations, and AI-native enterprise systems — the systems-of-record (ERP, CRM) and automations they run on included — that an operator can change without redeploying. This is the living knowledge base for how it works, mirrored from the engine's own docs. It grows one strong document at a time.
Concepts of Inflow
The mental model in one page: the primitives claim, the four actors of the platform, and how a visual workflow becomes something an engine can execute.
Read the concepts →Lab
developer toolsPages you drive rather than read. Everything runs in your browser against the same packages a plugin ships with.
Nodes
8 docsNodes
This is the hub for everything about Inflowenger nodes: what the primitive node types are, how to build each one, and — most importantly — how any node a user could want reduces to this small primitiv
From a frontend node to a primitive
This is the doc that explains why Inflowenger only needs a handful of primitive nodes. The promise the platform makes is strong:
Void node
A no-op node. It carries no rule data and executes nothing; the engine simply passes through it and follows its Next. It exists for structure, not behavior.
Code node
Runs a snippet of logic against the node's scoped context and writes the result back. This is the computation primitive: any pure transformation of context — reshaping data, computing a value, derivin
Contract node
The decision / control-flow primitive. A Contract node runs logic just like a Code node, but its output is interpreted as a list of tags that selects which of the node's outgoing transitions (Next ent
Extrinsic node
The "call my own backend" primitive. When the engine reaches an extrinsic node it publishes to a NATS subject you registered and uses the reply as the node's output — one request in, one response out.
Plugin node
The external adapter primitive, and the most powerful node type. It hands execution off to a live external process you own — running anywhere, holding its own connections and state — that the runtime
GoTo node
Jumps execution to a node in another (or the same) flow, then returns. This is the composition / reuse primitive: it lets one flow call into another the way a program calls a subroutine, so shared log
Compilers
2 docsCompilers
The engine only ever executes map[string]models.Node (see nodes.md). It never parses whatever JSON your visual editor produces. A compiler is the piece that sits in between: it takes your graph repres
Vue Flow / React Flow compiler
compilers/vueFlow is the shipped implementation of the general compiler contract, for graphs shaped like a Vue Flow export (a list of nodes plus a list of edges connecting them).
Architecture
1 docProtocol
1 docOn the roadmap
Docs we're bringing over next, as they firm up in the source repos.
Plugins, expanded
The full plugin lifecycle, adapters, and isolation model — beyond the node deep-dive.
Architecture, in depth
A stronger tour of Context, Workflows, Fractals, and Adapters.
Protocol v1 / v2
The wire-level Inflow protocol details, current and next.
Form Builder, documented
The x-inflow-ui reference to sit behind the Lab: every extension key, written down. The tool is live now — the prose is what is missing.
Jobs & Commands
How long-running work and commands flow through the system.