Core Concepts
Understand the building blocks of KX Axis — conversations, nodes, flows, and conditions.
Core Concepts
Conversations
A conversation is a single session between your agent and a user. Every conversation follows a flow — a directed graph of nodes that determines what happens next based on user input.
Nodes
Nodes are the atomic units of a flow. KX Axis has five built-in node types:
| Node | Purpose |
|---|---|
| Start | Entry point. Every flow has exactly one. |
| Message | Sends a message to the user. Supports Markdown and dynamic variables. |
| Condition | Branches based on user intent, variable values, or API results. |
| Action | Calls an external API, sends a webhook, or triggers a CRM update. |
| End | Terminates the conversation and records the outcome. |
Flows
A flow is a directed graph of nodes. You build flows in the Visual Workflow Builder by connecting nodes with edges. Edges can be:
- Unconditional — always follow this path
- Conditional — follow this path only when a rule evaluates to
true
Variables
Variables store dynamic data within a conversation. They can be:
- System variables — automatically set by KX Axis (e.g.
{{user.channel}},{{session.id}}) - Captured variables — extracted from user messages using NLU (e.g.
{{intent.name}},{{entity.email}}) - Custom variables — set by Action nodes from API responses
Use variables in Message nodes with double-brace syntax: Hello, {{user.firstName}}!
Intent Detection
KX Axis uses a built-in NLU layer to detect user intent. You define intents in the Intent Library with example phrases. The engine matches incoming messages to the closest intent and routes the flow accordingly.
Simulation
The Simulation Engine lets you test flows before deployment. You provide a sequence of synthetic user inputs, and the simulator runs the full flow — including API calls (in stub mode) — showing you every node decision.