Transitions define how the flow moves from one node to another. They control what happens next based on user input, context, or defined conditions.
Transitions

​
What is a Transition

A transition is a connection between nodes that determines the next step after a node is executed. Each node can have one or multiple transitions, enabling dynamic and flexible conversation paths.

​
Transition Settings

Each transition can be configured using the following fields:

​
Transition

Defines when this transition should be triggered.
  • Written as natural language instruction
  • Interpreted by the AI to decide routing
Example: The client wants to book a vehicle for a special event (e.g., prom, wedding).

​
Announcement

Message sent to the user before moving to the next node. Use this when:
  • you want to confirm understanding
  • you want to guide the user
  • you need a smoother transition
Example: 
Great, I’ll help you with that.
If left empty, the transition happens silently.

​
Extract Variables

Defines which values should be extracted from the user input during the transition. This allows the system to capture structured data while routing to the next node. Extracted variables can be reused later in the flow or passed into tools. Examples of extracted values:
  • event type
  • location
  • date
  • time
  • customer name
  • phone number
  • any other user-provided data

​
Extract Variable Fields

  • Name:
    Variable key used in the flow (e.g., event_type, pickup_location)
  • Description:
    Explains what value should be extracted     Examples: 
  Type of event the client is booking for.
  Pickup location address or place where the ride should start.
  • Possible Values:
    Comma-separated list of allowed values (e.g., wedding, prom, birthday, corporate)
  • Required:
    Indicates whether the value must be extracted before the transition proceeds
  • Remove:
    If enabled, the value will not be stored after extraction

​
How It Works

  1. Node finishes execution
  2. Transition conditions are evaluated
  3. Matching transition is selected
  4. Variables are extracted (if configured)
  5. Announcement is sent (if configured)
  6. Flow moves to the next node

​
Multiple Transitions

  • A node can have multiple transitions
  • The first matching transition is used

​
Default Behavior

If no condition matches:
  • use a fallback transition
  • prevent dead ends in the flow

​
Best Practices

  • Keep conditions clear and specific
  • Avoid overlapping logic
  • Always define a fallback path
  • Extract only necessary variables
  • Use announcements only when needed
  • Keep naming consistent across the flow

​
Notes

  • Transitions define the routing logic between nodes
  • Extracted variables allow structured data to persist across the flow
  • Proper configuration ensures stable and predictable behavior