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) |
allow_interruption | boolean | true | Whether the user can interrupt the agent while it’s speaking |
| 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
When allow_interruption is false, the agent disconnects the user’s audio input while speaking. Useful for scripted announcements or compliance-sensitive flows.
A flow without a Persona, LLM, TTS, and STT connected to the Framework node will fail to run.
