Classic Flow Library
The following document provides description about the different nodes offered within the flow designer canvas. This includes use cases and instruction on each node to inform users on how and where to use each node, along with their benefits.
It is also possible to use various objects and variables in many of these nodes. Using Context and Variables in Flow >
| Node | Category | Description |
|---|---|---|
 |
General | This node is a trigger node that is placed at the beginning of your flow. This tells the bot that this is the point where the process must begin. You must have one Start node per bot. Without a “Start” node, the BOT will be unable to trigger any of the flows it may have. |
 |
Send | A dialog node is used for creating messages that the bot will deliver to the end-user in messenger. Double click this node and write the message you would like your bot to deliver. Select “Done” to close this node and save your changes. |
 |
General | This node tells the bot to wait for customer message or interaction in messenger. The bot will not do anything until the user types something or selects an option from a feature in messenger. Using this, the bot is able to request and collect information from its end-users. See the “Function” node in “Know your Nodes (Advanced)” section to see how we can validate end-user input. |
 |
Input | This node can be used to deliver a list or menu to your end-users. Commonly this would provide a shortcut for users to begin a process such as “Reset Password”. By double clicking this node you will be able to add in the options you want the bot to present in this menu. Click “Done” to save your changes to this node. No matter how many options you have, there will always be an extra output port to the right of this node. This is for if the end-user types something, instead of selecting an option from the menu. This means you can create a flow for handling customer “free-type” messages. |
 |
General | There are two link nodes available: an input and output link. We can use these nodes to pass the bot to different parts of its flow – this is how we connect separate tabs within a bot. Learn More |
 |
General | In order to see the amount of traffic that is coming to a certain point within your bot, you can add a “Goal” node to the flow. This will collect data on when users reach that certain point within the flow, along with dates, times and the conversation ID. You can rename the goal to be recognizable by your business by double clicking the node and giving it a name within the text input field. |
 |
Input | Sends the conversation to the next worker in the bot chain. If no worker after it matches on the intent or event, a missed input will be reported. |
 |
Integration | Calls an API connector configured in BaaS and routes based on response codes. Will automatically pull mappings out of the BaaS’s request mapping configurations |
 |
Start | Starts flow when triggered using a botnet action. |
 |
Send | This node allows for mark-up language to be entered, specifically to add features into your flow which can be displayed in messenger. Learn More |
 |
Send | The host webpage of our ServisBOT Messenger can receive notifications from our server (internally known as Host Notification). Host Notifications can be sent by as a Botnet Action or Node and are emitted to the host webpage by our messenger. To listen out for these notifications you can do the following. |
 |
Start | Releases the conversation from the current flow. If it was triggered by a botnet action, it will return the conversation to the normal state. |
 |
End | This node represents a sucessful bot resolution. Records a goal that the bot completed it’s mission, and releases the bot from the conversation. When enabled, previous message events will be passed forward to the next bot. Learn More |
 |
End | Transfers control to another Bot or Worker. When the next bot calls botMissionDone, the conversation will return to this bot. When pushing to NLP based bots, it is possible to trigger a specific intent immediately after arriving at the newly routed bot. |
 |
End | Transfers control to another Bot. Control will stay with the other bot unless it is intentionally returned. |
 |
NLP | This node will use the configuration in a secret to detect intent/slots in an external NLP service from the context of Classic Flow. |
 |
Input | Enhanced version of the markupInteraction node with more standard responses from interaction events and handling of VTL |
 |
Send | New and improved content node. This node will send content from the CMS, using the key value of a CMS item you want to send. If lang is set in the bots context to a locale or language copy available to that key, the bot will automatically use that language variant, otherwise it will use en. CMS content can be previewed and edited all from within the node. Learn More |
 |
General | This node can be used to update/change (promote) particular values related to a conversation inside of ServisBot |