On this page, we'll cover the following topics:
What is a Node?
Nodes are the interlinked building blocks of a bot. Each node acts like a gatekeeper who detects user inputs, sends out appropriate responses, and directs users to the next node. They are the points where conversation converges or diverges basis the information users input to the bot. Nodes are comprised of several important sub-components, which house important pieces of information. Read on in this section to learn more about the significance of the components User Says, Bot Says, and Entities, and APIs.
To jump straight to reading about any of the sub-components of nodes, click on the link in the subcomponents section of any node.
Otherwise, keep reading below to learn about the different node types and how to get started creating nodes.
Different Types of Nodes
The bot builder tool provides three types of nodes. Each node has a specific purpose and the different nodes can be used together in different combinations based on the use case.
The three types of nodes are:
- Static Node
- Code Node
- Output Node
Purpose and Subcomponents of Static Nodes
The purpose of a static node is to present static information to the user like greeting message, menu options etc and to then collect infromation from the user that is required to perform business logic.
Purpose and Subcomponents of Code Nodes
The purpose of a code node is to take the input collected from the static and use custom code to perfrom business logic on it. The advantage of moving this to a seperate node is that it helps you in seperating out the code and non-code features of bot building.
The code node takes the input from the static node in a JSON format with certain parameters. It processes this input JSON according to business logic and returns an output JSON.
Additionally, this gives you more power with respect to what you can do with the output from the integration code as we will in the next section and the connections section.
Purpose and Subcomponents of Output Nodes
The purpose of output node is to take the JSON output from the code node and build dynamic bot says that use parameters from this output in the HSL.
Bot Builders can take advantage of an easy-to-use JSON picker in the bot says section to build the HSL using parameters from the output JSON.
Creating a Node
You will create your nodes within a sub-story. To make a node, click the sub-story on the left-hand-side. Now, click on the 'Add Nodes' button just below your sub-story title, as depicted here:
This will open a sidebar, as shown below, on the left-hand side of the graph. You can drag and drop the node you want from this sidebar
Once you drag and drop any of the node type from the sidebar, a new sidebar is opened with the RHS of the ndoe type you selected. You will need to fill in some information about the node before saving it.
You'll need to add the following inputs:
Node Name: The label that will appear on the node on the Mogambo graph.
System Name: The system name is used to uniquely identify the node in the backend. Only underscores and capital case alphanumeric characters are allowed in this field.
Node Type: Use node type to indicate if a node is a Start Node or an End Node. Start Nodes indicate that this is the node that will initiate a conversation, while an End Node is the last node in a conversation. When an end node is reached, and that node does not have further connecting nodes, we internally mark this conversation as 'complete,' which helps when tracking user activity.
Tip: When the user is in the middle of a conversation and the system cannot find a match to the connecting nodes, our system will go over all the start nodes to see if it can find a match to what the user said.
Status: Indicate whether the node will be active or inactive. When you are first making a bot, we'll assume all the nodes you create are active. Instances when you will deactivate nodes will arise later on.
Click 'Save' when done.
Post creation of a node, the node will be displayed as depicted below: