Execute Flow (Realtime)

The Execute Flow block acts as a powerful orchestrator. It allows you to trigger a separate saved flow (for example another Agentflow V2 graph) from within the realtime-v1 canvas.

Modularity in Voice Deployments

When creating complex IVR environments or SIP Call Center logic, stuffing everything into a single graph is an antipattern that causes LLM confusion.

For instance, your primary Realtime Canvas manages greetings and caller intent. If the caller requests technical support, the graph hits an Execute Flow node that maps to an entirely independent internal Flow ID.

Network Behavior

1. State preservation: The Execute Flow node carries the realtime session id and related persistence context into the child flow.
2. Streaming Integrity: Even while a downstream Flow executes, the WebSocket connection with the Unity Call Center app is perfectly maintained. It will pause the audio queue seamlessly, execute the secondary flow, and resume delta responses without triggering the 60s inactivity drop.