Nodes

When building conversational bots in Botnex, you use a visual flow editor made up of different node types. Each node type serves a specific purpose in your bot's logic and user experience. Understanding these node types will help you design effective, engaging, and maintainable bot flows.

Start Node

What is it?
The Start Node is the entry point of your flow. Every flow must have exactly one Start Node, which determines where the conversation begins when a user enters this part of your bot.

How to use it:

• Place the Start Node at the beginning of your flow
• Connect it to the first Story Node or Transition Node to define what happens when the flow starts
• Use the Start Node to set up initial variables or context for the conversation

Best practices:

• Only one Start Node per flow
• Always connect it to the next logical step
• Keep the initial setup simple and focused

Story Node

What is it?
A Story Node represents a step in the conversation where the bot delivers a message, asks a question, or presents information to the user. Think of it as a "scene" or "page" in your bot's conversation flow.

How to use it:

• Create the main content of your bot: greetings, instructions, questions, or informational messages
• Add rich content, buttons, images, or quick replies to enhance user engagement
• Connect Story Nodes to other nodes to define what happens next based on user input or actions

Best practices:

• Break down complex conversations into multiple Story Nodes for clarity
• Use clear, concise language that matches your brand voice
• Leverage buttons and quick replies to guide users toward desired actions
• Keep each Story Node focused on a single purpose or message

Transition Node

What is it?
A Transition Node controls the flow of the conversation based on conditions, user choices, or logic. It acts as a decision point, allowing you to branch the conversation in different directions based on various criteria.

How to use it:

• Evaluate user responses, check variables, or implement conditional logic
• Connect a Transition Node to multiple Story Nodes or other nodes, each representing a different conversation path
• Set up conditions in the Transition Node to determine which path the conversation should follow

Best practices:

• Use Transition Nodes to keep your flows organized and maintainable
• Clearly label each outgoing path for easy understanding and debugging
• Combine with Story Nodes to create dynamic, personalized conversations
• Test all possible paths to ensure smooth user experiences

How Nodes Work Together

Here's a typical flow pattern:

1. Start Node: The user enters the flow
2. Story Node: The bot greets the user and asks a question
3. Transition Node: The bot evaluates the user's answer and routes them to the appropriate next step
4. Story Node: The bot provides a response based on the chosen path

This pattern can repeat and branch as needed to create sophisticated conversation flows.

Node Types Summary

Node Type	Purpose	Best Used For
Start	Entry point of a flow	Beginning a new conversation or sub-flow
Story	Deliver messages or ask questions	Showing information, collecting input, presenting media
Transition	Branch logic based on conditions or choices	Routing users, handling logic, making decisions

Tips for Effective Node Design

• Plan Your Flow: Sketch out your conversation flow before building to identify the nodes you'll need
• Keep It Simple: Start with basic flows and add complexity gradually
• Test Frequently: Use the simulator to test your flows as you build them
• Use Descriptive Names: Give your nodes clear, descriptive names to make your flows easier to understand and maintain
• Consider User Paths: Think about all the ways users might respond and plan for those scenarios

By combining these node types thoughtfully, you can build powerful, flexible conversational flows in Botnex that guide users, collect information, and deliver engaging experiences that meet your business goals.