Availability by Variable Type
* Only if the current node runs after the node that created the variable.
Flow Position Rules (Flow Agent)
- Predecessors only: A node sees variables only from nodes that run before it.
- Execution paths: All possible paths are considered when computing predecessors.
- Global nodes: Nodes with
isGlobal: truesee only system and custom variables. - Caching: Availability is cached per node and refreshed when the flow changes.
Example Flow
Single Prompt Agent Variables
Single prompt agents are standalone conversational agents that don’t use the flow builder. They have a simplified variable model optimized for quick deployment and simple use cases.Variable Availability
How Custom Variables Work in Single Prompt Agents
Custom variables in single prompt agents act as parameters that configure the agent: Definition (Variables Panel):Key Differences from Flow Builder Agents
Use Cases for Single Prompt Agents
Good for:- Simple Q&A agents
- Information lookup agents
- Basic customer service
- FAQ bots
- Quick prototypes
- Agents with minimal state
- Multi-step workflows
- Data collection and processing
- API integrations with variable extraction
- Complex conditional logic
- State management across multiple steps
Configuration Example
Variables Panel (Custom Variables):- ✅
working_hours,support_tier,escalation_enabled(custom) - ✅
agent_name,current_time,current_date,user_number,direction(system)
When to Upgrade to Flow Builder
Consider upgrading to a Flow Builder agent when you need to:- Extract data from conversations (AI extraction)
- Integrate with APIs and parse responses (toolpath extraction)
- Use conditional branching or multi-step logic
- Collect structured information across nodes
- Use DTMF capture or static variables
Variable Categories & Display
Variables are grouped for the UI:
Displayed per variable: name, type, source (for extracted/static), description, default/example value.
Context-Aware Recommendations
The UI can suggest variables based on node type and content:- Conversation: e.g.
customer_name,phone_number,appointment_date,issue_description - Tool: e.g.
api_response,status_code,response_data,error_message - Transfer: e.g.
transfer_reason,customer_context,conversation_summary