|
Node |
Action Node |
|---|---|
|
Description |
Actions nodes |
| Title | Description |
|---|---|
| Change Bot Role |
This Change Bot Role node can be used to change the role of the bot present in the conversation. |
| Assign Bot |
This Assign Bot node adds a bot in the conversation with the specified role. |
| Remove Channel Session |
The Remove Channel Session node can be used to remove a channel session from the current conversation. You can remove current, last used, all or a specific channel by its channel type. |
| Revoke Bot |
Revoke Bot node can be used to remove the bot from the conversation. |
| Update Conversation Data |
The Update Conversation Data node can be used to store custom data within a conversation. Up-to 10 key-value pairs can be stored within conversation data of a single conversation. |
| Open External Gadget |
The Open External Gadget node can be used to open a gadget with custom URL for the current or all agents on Agent Desk. |
| Set Slot |
The Set Slot node can be used to create/update a slot linked to a room. A slot is a key-value pair that can be used to store any type of data. Whenever a controller receives an event, it automatically attach the slots linked to that room with the |
| General Action |
The General Action node can be used to request conversation manager for custom actions. |
| Remove All Agents |
This node can be used to removes all agents from the current conversation. You can also specify the reason for removing the agents. |
| Dispatch Find Agent |
The Dispatch Find Agent node builds and dispatches a |
| Determine Queue |
The Determine Queue node is used to determine the queue selector (type and value) for routing and writes it to the message. |
| Extract Data |
The Extract Data node is used to extract/normalize key fields from the incoming payload into top-level |
| End Conversation |
Terminates the conversation and removes all the channel sessions. |










