Framework Node
The Framework node is the heart of every Voiceblox flow. It receives all component connections, acts as the entry point for the conversation step chain, and determines the runtime.
Every flow must have exactly one Framework node.
Providers
| Provider | Status |
|---|
livekit | ✅ Stable |
pipecat | 🔜 Coming soon |
Parameters
| Parameter | Type | Default | Description |
|---|
provider | enum | livekit | Runtime framework (livekit) |
interruption_mode | enum | off | Interruption: off (disabled) or on (adaptive ML-based detection for cascade, VAD for realtime) |
| Handle | Type | Max connections | Description |
|---|
persona_in | persona | 1 | Agent identity and system prompt |
llm_in | llm | 1 | Language model |
tts_in | tts | 1 | Text-to-speech engine |
stt_in | stt | 1 | Speech-to-text engine |
avatar_in | avatar | 1 | Visual avatar (optional) |
transfer_in | framework | unlimited | Incoming transfers from Transfer nodes |
tools_in | context | unlimited | MCP servers and Exa search tools |
Output handle
| Handle | Type | Description |
|---|
output | control | Connects to the Start node |
Interruption behavior
The interruption_mode parameter controls how the agent handles user speech while it is speaking:
- Off — The agent cannot be interrupted. Useful for scripted announcements or compliance-sensitive flows.
- On — The agent can be interrupted by the user. For cascade agents, this uses adaptive ML-based interruption handling that distinguishes true interruptions from conversational backchanneling (e.g. “uh-huh”, “okay”). For realtime agents, this uses VAD-based interruption detection.
A flow without a Persona, LLM, TTS, and STT connected to the Framework node will fail to run.
