GETTING STARTED
Kore.ai XO Platform
Virtual Assistants Overview
Natural Language Processing (NLP)
Concepts and Terminology
Quick Start Guide
Accessing the Platform
Navigating the Kore.ai XO Platform
Building a Virtual Assistant
Help & Learning Resources
Release Notes
Current Version
Recent Updates
Previous Versions
Deprecations
Request a Feature
CONCEPTS
Design
Storyboard
Overview
FAQs
Conversation Designer
Overview
Dialog Tasks
Mock Scenes
Dialog Tasks
Overview
Navigate Dialog Tasks
Build Dialog Tasks
Node Types
Overview
Intent Node
Dialog Node
Dynamic Intent Node
GenAI Node
GenAI Prompt
Entity Node
Form Node
Confirmation Node
Message Nodes
Logic Node
Bot Action Node
Service Node
Webhook Node
Script Node
Process Node
Agent Transfer
Node Connections
Node Connections Setup
Sub-Intent Scoping
Entity Types
Entity Rules
User Prompts or Messages
Voice Call Properties
Knowledge AI
Introduction
Knowledge Graph
Introduction
Terminology
Build a Knowledge Graph
Manage FAQs
Knowledge Extraction
Import or Export Knowledge Graph
Prepare Data for Import
Importing Knowledge Graph
Exporting Knowledge Graph
Auto-Generate Knowledge Graph
Knowledge Graph Analysis
Answer from Documents
Alert Tasks
Small Talk
Digital Skills
Overview
Digital Forms
Digital Views
Introduction
Widgets
Panels
Session and Context Variables
Context Object
Intent Discovery
Train
NLP Optimization
ML Engine
Overview
Model Validation
FM Engine
KG Engine
Traits Engine
Ranking and Resolver
Training Validations
NLP Configurations
NLP Guidelines
LLM and Generative AI
Introduction
LLM Integration
Prompts & Requests Library
Co-Pilot Features
Dynamic Conversations Features
Kore.ai XO GPT Model
Intelligence
Introduction
Event Handlers
Contextual Memory
Contextual Intents
Interruption Management
Multi-intent Detection
Amending Entities
Default Conversations
Conversation Driven Dialog Builder
Sentinment Management
Tone Analysis
Default Standard Responses
Ignore Words & Field Memory
Test & Debug
Overview
Talk to Bot
Utterance Testing
Batch Testing
Conversation Testing
Conversation Testing Overview
Create a Test Suite
Test Editor
Test Case Assertion
Test Case Execution Summary
Glossary
Health and Monitoring
NLP Health
Flow Health
Integrations
Actions
Actions Overview
Asana
Configure
Templates
Azure OpenAI
Configure
Templates
BambooHR
Configure
Templates
Bitly
Configure
Templates
Confluence
Configure
Templates
DHL
Configure
Templates
Freshdesk
Configure
Templates
Freshservice
Configure
Templates
Google Maps
Configure
Templates
Here
Configure
Templates
HubSpot
Configure
Templates
JIRA
Configure
Templates
Microsoft Graph
Configure
Templates
Open AI
Configure
Templates
Salesforce
Configure
Templates
ServiceNow
Configure
Templates
Stripe
Configure
Templates
Shopify
Configure
Templates
Twilio
Configure
Templates
Zendesk
Configure
Templates
Agents
Agent Transfer Overview
Custom (BotKit)
Drift
Genesys
Intercom
NiceInContact
NiceInContact(User Hub)
Salesforce
ServiceNow
Configure Tokyo and Lower versions
Configure Utah and Higher versions
Unblu
External NLU Adapters
Overview
Dialogflow Engine
Test and Debug
Deploy
Channels
Publishing
Versioning
Analyze
Introduction
Dashboard Filters
Overview Dashboard
Conversations Dashboard
Users Dashboard
Performance Dashboard
Custom Dashboards
Introduction
Custom Meta Tags
Create Custom Dashboard
Create Custom Dashboard Filters
NLP Insights
Task Execution Logs
Conversations History
Conversation Flows
Conversation Insights
Feedback Analytics
Usage Metrics
Containment Metrics
Universal Bots
Introduction
Universal Bot Definition
Universal Bot Creation
Training a Universal Bot
Universal Bot Customizations
Enabling Languages
Store
Manage Assistant
Team Collaboration
Plan & Usage
Overview
Usage Plans
Templates
Support Plans
Invoices
Authorization
Conversation Sessions
Multilingual Virtual Assistants
Get Started
Supported Components & Features
Manage Languages
Manage Translation Services
Multiingual Virtual Assistant Behavior
Feedback Survey
Masking PII Details
Variables
Collections
IVR Settings
General Settings
Assistant Management
Manage Namespace
Data
Overview
Data Table
Table Views
App Definitions
Data as Service
HOW TOs
Build a Travel Planning Assistant
Travel Assistant Overview
Create a Travel Virtual Assistant
Design Conversation Skills
Create an ‘Update Booking’ Task
Create a Change Flight Task
Build a Knowledge Graph
Schedule a Smart Alert
Design Digital Skills
Configure Digital Forms
Configure Digital Views
Train the Assistant
Use Traits
Use Patterns
Manage Context Switching
Deploy the Assistant
Use Bot Functions
Use Content Variables
Use Global Variables
Use Web SDK
Build a Banking Assistant
Design Conversation Skills
Create a Sample Banking Assistant
Create a Transfer Funds Task
Create a Update Balance Task
Create a Knowledge Graph
Set Up a Smart Alert
Design Digital Skills
Configure Digital Forms
Configure Digital Views
Add Data to Data Tables
Update Data in Data Tables
Add Data from Digital Forms
Train the Assistant
Composite Entities
Use Traits
Use Patterns for Intents & Entities
Manage Context Switching
Deploy the Assistant
Configure an Agent Transfer
Use Assistant Functions
Use Content Variables
Use Global Variables
Intent Scoping using Group Node
Analyze the Assistant
Create a Custom Dashboard
Use Custom Meta Tags in Filters
Migrate External Bots
Google Dialogflow Bot
APIs & SDKs
API Reference
API Introduction
Rate Limits
API List
koreUtil Libraries
SDK Reference
SDK Introduction
SDK Security
SDK Registration
Web Socket Connect and RTM
Installing the BotKit SDK
Using the BotKit SDK
SDK Events
SDK Functions
SDK Tutorials
BotKit - Blue Prism
BotKit - Flight Search Sample VA
BotKit - Agent Transfer
Widget SDK Tutorial
Web SDK Tutorial
ADMINISTRATION
Introduction to Admin Console
Administration Dashboard
User Management
Add Users
Manage Groups
Manage Roles
Data Tables and Views
Assistant Management
Enrollment
Invite Users
Send Bulk Invites
Import User Data
Synchronize Users from AD
Security & Control
Using Single-Sign On (SSO)
Two-Factor Authentication (2FA)
Security Settings
Cloud Connector
Analytics
Billing
  1. Home
  2. Docs
  3. Virtual Assistants
  4. Builder
  5. Dialog Task
  6. Bot Action Node

Bot Action Node

The Bot Action Node can be used for any action that the bot is expected to perform without interaction with the user. It can be used as a container for service, script, webhook, logic and process nodes. This node type has been introduced in v. 9.0 of the XO Platform.

This article takes you through the functionality of the primary Bot Action node. For information on contained nodes, please see their respective documentation. 

Features

The Bot Action Node allows you to: 

  • Ability to manage the actions that the VA needs to perform without user intervention.
  • Acts as a container for nodes relevant to the actions that the VA needs to perform. This simplifies the management process for the entire assistant, by allowing developers to designate specific nodes to specific actions.

Add the Node

Setting up a Bot Action node in a dialog task involves the following steps:

  1. Open the dialog task to which you want to add the Bot Action node.
  2. Add the Bot Action node in the designated place. For steps related to adding nodes, refer here.
  3. The Bot Action  node Properties panel is displayed with the Component Properties tab selected by default.
  4. You can use the +/ against the node to Expand/Collapse the node
  5. Once you expand a Bot Action node, you have the option to add various nodes – service, script, webhook, logic and/or process nodes. Please refer to the individual nodes for configuration details.


Configure the Node

The following sections detail the properties for this node in the new dialog builder, introduced in v9.0 of the platform. For details related to the legacy dialog builder, please refer here.

Component Properties

Note: All changes made to the Component Properties tab will affect all instances of the node, across Dialog Tasks. 

 

To configure the Component Properties tab, please follow the steps below:

  1. On the Component Properties tab, under the General Settings section, you can modify the Name, Display Name, and Description of the node.
  2. In the Variable Namespaces section (v8.0), associate the variable namespaces to execute this node and its transitions. This option is visible only when the variable namespace is enabled for the assistant. You can go with the task level settings or customize it for this node. For more information, refer to Managing Namespace.


Connections Properties

The Connection Properties of a Bot Action node allow you to configure which node within the group is initiated first, and which node to trigger next, right after the VA goes through the nodes within the Bot Action node group.

You can configure the following types of connections: 

  • Bot Action Node Connections: Choose the first node to be initiated within the Bot Action group. You can select any of the nodes in this Bot Action group.
  • Bot Action Group Connections: Choose the nodes to be initiated after executing the Bot Action group. You can select any of the nodes outside this Bot Action group.

For Bot Action Group Connections, you can configure If-Else conditions. To do so, please follow the steps outlined in Adding IF-Else Conditions to Node Connections.


Manage Contained Nodes

As mentioned, nodes contained by Bot Action nodes include;  service, script, webhook, logic and/or process nodes.

To manage the nodes contained within a Bot Action node, please follow the steps below:

  • Click the expand (+) button next to the Bot Action node. The primary nodes panel will be replaced with the Bot Action nodes panel.
  • The Bot Action node shows all of its containing nodes as a group. Add any node from here, using either the “+” sign or drag and drop. Bot Action nodes provide the following options: On the left side of the node there is an Expand (+) button if the node is collapsed, and a Collapse (-) button if the node is expanded. Nodes can also be collapsed using the Close (x) button on the top right.


Manage Connections for Contained Nodes

Nodes inside the bot action node cannot be connected directly to any node outside the bot action group. For such nodes, the following connections can be configured:

  • Any node within the corresponding bot action node;
  • Not Connected;
  • End of Bot Action – this would take the bot flow to the node connected to the bot action node;

Bot Action Node

The Bot Action Node can be used for any action that the bot is expected to perform without interaction with the user. It can be used as a container for service, script, webhook, logic and process nodes. This node type has been introduced in v. 9.0 of the XO Platform.

This article takes you through the functionality of the primary Bot Action node. For information on contained nodes, please see their respective documentation. 

Features

The Bot Action Node allows you to: 

  • Ability to manage the actions that the VA needs to perform without user intervention.
  • Acts as a container for nodes relevant to the actions that the VA needs to perform. This simplifies the management process for the entire assistant, by allowing developers to designate specific nodes to specific actions.

Add the Node

Setting up a Bot Action node in a dialog task involves the following steps:

  1. Open the dialog task to which you want to add the Bot Action node.
  2. Add the Bot Action node in the designated place. For steps related to adding nodes, refer here.
  3. The Bot Action  node Properties panel is displayed with the Component Properties tab selected by default.
  4. You can use the +/ against the node to Expand/Collapse the node
  5. Once you expand a Bot Action node, you have the option to add various nodes – service, script, webhook, logic and/or process nodes. Please refer to the individual nodes for configuration details.


Configure the Node

The following sections detail the properties for this node in the new dialog builder, introduced in v9.0 of the platform. For details related to the legacy dialog builder, please refer here.

Component Properties

Note: All changes made to the Component Properties tab will affect all instances of the node, across Dialog Tasks. 

 

To configure the Component Properties tab, please follow the steps below:

  1. On the Component Properties tab, under the General Settings section, you can modify the Name, Display Name, and Description of the node.
  2. In the Variable Namespaces section (v8.0), associate the variable namespaces to execute this node and its transitions. This option is visible only when the variable namespace is enabled for the assistant. You can go with the task level settings or customize it for this node. For more information, refer to Managing Namespace.


Connections Properties

The Connection Properties of a Bot Action node allow you to configure which node within the group is initiated first, and which node to trigger next, right after the VA goes through the nodes within the Bot Action node group.

You can configure the following types of connections: 

  • Bot Action Node Connections: Choose the first node to be initiated within the Bot Action group. You can select any of the nodes in this Bot Action group.
  • Bot Action Group Connections: Choose the nodes to be initiated after executing the Bot Action group. You can select any of the nodes outside this Bot Action group.

For Bot Action Group Connections, you can configure If-Else conditions. To do so, please follow the steps outlined in Adding IF-Else Conditions to Node Connections.


Manage Contained Nodes

As mentioned, nodes contained by Bot Action nodes include;  service, script, webhook, logic and/or process nodes.

To manage the nodes contained within a Bot Action node, please follow the steps below:

  • Click the expand (+) button next to the Bot Action node. The primary nodes panel will be replaced with the Bot Action nodes panel.
  • The Bot Action node shows all of its containing nodes as a group. Add any node from here, using either the “+” sign or drag and drop. Bot Action nodes provide the following options: On the left side of the node there is an Expand (+) button if the node is collapsed, and a Collapse (-) button if the node is expanded. Nodes can also be collapsed using the Close (x) button on the top right.


Manage Connections for Contained Nodes

Nodes inside the bot action node cannot be connected directly to any node outside the bot action group. For such nodes, the following connections can be configured:

  • Any node within the corresponding bot action node;
  • Not Connected;
  • End of Bot Action – this would take the bot flow to the node connected to the bot action node;

Menu