Configure Workflow Nodes
Dialogue and collection nodes
Consecutive Conversation nodes retain the same active Agent. A direct Agent or Subagent creates a new active Agent; it remains active through normal nodes and later Conversation stages until another handoff occurs.
Avatar scope
Open the Avatar tab on Start, Agent, or Subagent to choose one of these scopes:
Selected avatars use their saved visual settings. The node does not override posture, background, or quality. A selected avatar requires an available organization LiveAvatar credential for visual web sessions; it does not affect phone calls.
Inherited assistant settings
The workflow configuration supplies its global prompt, default provider configuration, compliance policy, retention settings, and analysis selection. Direct Agent nodes may override their model, voice, and transcriber for a stage; Conversation nodes retain the active Agent configuration. The Start node can override the inheritedstart_speaking_plan for the session.
For provider IDs, credentials, vocabulary, fallbacks, voice delivery, audio environment, and speaking-plan fields, use the Assistant configuration reference. Workflow compliance and analysis are stored in each published version.
Routing and action nodes
Completion and timeout routing
Conversation, Agent, and Subagent nodes complete when their active Agent callscomplete_step with outcome data. Configure their node instruction and fallback edge. Data Tasks use their typed update_<field> tools instead; their Advanced panel only controls timeout/recovery.
Do not use a Conversation node to collect a finite routing value such as language or department. Use a Choice field in a Data Task so the stored value is validated and deterministic.
Conversation routing patterns
Use a Conversation node for an open-ended exchange or intent classification, not for the action itself. State the caller-facing question, supported intents, one clarification rule, and that the node must not perform the action or expose route names. Complete a route only after the caller gives a clear answer. Use typed Data Tasks for finite information. For consequential actions such as transfers, card blocks, bookings, or cancellations, collect facts first, read them back, and require explicit confirmation in a separate routed Conversation before the API request. After a completed service, use an “Anything else?” route back to the main menu or End Call. This prevents an informational conversation from ending a call immediately after its first answer.Connection checklist
- Every Conversation, Agent, Subagent, and Task has an unconditional outgoing edge.
- Logic conditions reference variables produced earlier in the graph.
- Choice conditions use the stored key, not a spoken alias:
language equals yo. - Every terminal branch reaches End Call or Transfer Call.
- External-resource nodes have organization resources selected before test or publish.