Node Inspector is the section appearing on the right whenever you click to edit any node. It is the place where you can set your message responses.
|Name||The name of this node||Y|
|Description||Description of this node||N|
|Priority||The sequence of node order, smaller the number earlier the order||N|
|Color||Label this node with a color||N|
- Priority must be whole numbers
- You may categorize different nodes into groups by colors
A Trigger is a way to notify the chatbot to send respective messages. Usually, there are four ways of calling a node:
- Developer-defined payload
- Text entered by users
- URL parameters in Chatbot's short link
- Comment on Facebook post by users
It is a logical group of conditions that set to initiate actions of a specific node. You may specify each trigger with the logical operators “AND” or “OR”.
- And: conditions that are mutually inclusive
- Or: conditions that are mutually exclusive
There are two types of condition you can specify:
- Condition: Single condition that specifies one single property
- Condition Group: A group of conditions that specify the same property but with different values
|Name||The name of this trigger||Y|
|Description||Description of this trigger||N|
|Conditions||Single condition or condition groups||N|
- Put the trigger type as the first condition, i.e. payload, text, URL or comment
- Pick the correct conjunction, i.e. AND or OR, to show the correct relations
- Put the trigger content as the second condition, i.e. the payload name, the text keyword
It is possible for one node to have multiple triggers. However, if the triggers are of different types, it is suggested to break them down into different global nodes so as to better track user journey.
A Response is the message your chatbot would send to your users once they trigger this node. You may set one or more responses in one single node.
For different types of response objects, please see Messages Types.
- Set no more than 3 responses in one node, otherwise the user will receive a bunch of messages at one time
Actions are divided into two types:
- Pre-action: Set pre-action if there is any action you would like to perform BEFORE sending responses to users
- Post-action: Set post-action if there is any action you would like to perform AFTER sending responses to users.
We suggest to set one post-action as default: Save CompositeId. This would help you track the position of your users within the conversation flow so you could read their footprint.
Set Redirect if you want to redirect to any of the other nodes in the same or any other trees. This item is not compulsory and is only applicable when you want to send responses of other nodes within or across trees.
|Tree||The tree you want to redirect to||Y|
|Node||The node you want to redirect to||Y|
|Send Response After Redirect||Tick to send response of that redirected node||N|