Skip to main content
The Dialog Builder uses nodes and transitions to make the necessary connections between the components of your conversation. This article overviews the available node types, transitions, and context object information.

​
How do Nodes and Transitions Work?

Nodes let you visualize the entire conversation flow as a map on a canvas. Transitions add conditional logic to control how the conversation moves between nodes. Together, sequences, nodes, and transitions enable AI Agents to automate tasks while preserving a seamless user experience.

​
Node Types

You can add the following nodes to Agent Flows (dialog tasks), based on your requirements:

​
Primary Nodes

​
Other Nodes

​
Component Transitions

A Dialog Task builds a task flow with different nodes connected by transitions. Dialog Task transitions depend on conditions that use business-defined evaluation criteria to take the next steps within the Dialog Task flow. You define If-then-else conditions using a set of predefined operators. For each component, you must specify a fallback condition. How you represent a transition depends on the component type you are defining, and component type-specific transitions are described in the documentation topic for each component type. You can use the following operators to write conditions:
  • Exists
  • Doesn’t exist
  • Equals to
  • Greater than equals to
  • Less than equals to
  • Not equals to
  • Greater than
  • Less than
  • Contains
Learn more about setting up node connections.

​
Environment Variables

Environment Variables are global, reusable components which can be used in multiple places to define the app configuration. Every Environment Variable is a key-value pair. The Variable Keys can be used at various places in the app configuration. The platform will resolve/replace the Variable Keys with Variables Values during the conversation. Some of the typical use cases where a developer can use environment variables are:
  • To manage the app across environments having different endpoint URLs. The app can be exported and imported based on the environment, and the infrastructure team will need to modify only the variable configuration file.
  • To manage Conditions in the Dialog Node Transitions. Both the left-hand side and the right-hand side of the transition condition use Environment Variables.
You must enter dynamic variables without braces. For example, Environment variables as env.value, Content variables as content.value, and Context variable as context.entities.entityname. For more information, see the Adding IF-Else Conditions to Node Connections article.
  • To define and manage the bot response that’s repeated within the app configuration as variables.
  • Authorization Token.
  • Channel-related tokens and URLs.