Action Nodes

Actions are non-interactive nodes that can be used to perform a specific task (background action). These nodes will not display any messages to the user while having a conversation but they run the said tasks in the background.

Different types of action nodes that will be discussed in this article are:

  1. General
  2. Code Based
  3. Language & Notification
  4. Nodes available only for Workflow

1. General action nodes#

1.1 Send event#

Record an event with this node. Events are used to record specific actions or capture an important conversion, click here to learn more.

1.2 Send OTP#

Send OTP to a phone number with this node.

  • Ask and Store the phone number in a variable.
  • Select the variable name (phone) on the Send OTP node.

Following text message will be sent to the respective number.

1.3 Verify OTP#

Store the entered OTP as a variable and verify it with this node.

Success and Fallback cases must be handled by connecting them to other nodes to continue the flow. That is, node connected to success will be executed if the OTP is matched, otherwise, node connected to fallback will get executed.

1.4 Document search#

Answer user queries referring to the available documents from your knowledge base using this node.


Document Search action node is used to answer user query at any point in the flow (or fallback) from documents uploaded in the Knowledge base (This node shows results from configured Document Cognition).

  • You can select a variable containing a search query
  • You can also choose to add metadata filters (optional) to your query (the filters you tagged your documents with will show in dropdown).
  • You can branch flow from here based on whether any results were found in the documents (success) or not (failure).
  • There is no store output here, as the results are directly shown in carousels.
  • In node settings, you can configure the total no. of results shown, the total number of results per document and messages shown while showing results/reporting failure.

1.5 Execute flow#

This node is available for voice bots.

Enter another flow with this node. For example, in the below flow, based on the entered user reply the conversation gets directed to other flows. Once that flow is executed, control comes back to the current flow.

1.6 Delay#

Add a time delay between components with this node. Select the number of minutes/hours you want the bot to wait for before executing the next node.


Alternative method is to set the delay on each of the nodes:

1.7 Raise ticket#

Raise ticket is used in order to connect bot user to the human agent. Connect the user to an agent after collecting info and query with this node.

This simple UI node can be used to set up basic & advanced scenarios such as Working Hours, Agent Availability, voice/video calling, etc required to create a ticket.

Raise ticket outputs#

  1. Ticket Closed - This essentially is bot behaviour after the Agent closes a ticket (i.e. s/he has resolved user query).
  2. Error - This can be used as a generic message in any case ticket creation is not successful. For customised messages, specific errors event hub can be configured.

Raise ticket response#

Raise Ticket action node returns an object response as shown below. You can parse important information from this response to store it in a database or use it on another flow.

"tags": [],
"responded": false,
"ticketType": "livechat",
"ticketCsatScore": null,
"agentCsatScore": null,
"assignedByAdmin": false,
"manualAssignment": false,
"lastAgentMessageTime": null,
"lastUserMessageTime": null,
"lastBotMessageTime": null,
"userActiveStatus": null,
"agentActiveStatus": null,
"replyCount": 0,
"voiceCall": false,
"sipCall": false,
"agentCurrentHandlingTicketsCount": 0,
"autoStartCall": false,
"autoTranslate": false,
"autoDetectLanguage": false,
"_id": "6156df377b7bb14e16bae116",
"botId": "YOUR_BOT_ID_HERE",
"uid": "106265078787462873391306131746",
"source": "yellowmessenger",
"issue": "ISSUE_TITLE_HERE",
"priority": "MEDIUM",
"severity": "MEDIUM",
"contact": {
"phone": "1234567890",
"name": "CUSTOMER_NAME",
"assignedTo": "community_yello_ai",
"sessionId": "5b8a665e69dbc5c451d88bf0",
"userLanguage": "en",
"ticketId": "100001",
"logs": [],
"timestamp": "2021-10-01T10:13:11.657Z",
"reassignmentLog": [],
"collaborators": [
"_id": "6156df377b7bb15d9fbae11a",
"username": "community_yello_ai",
"xmppUsername": "user_1624003758958",
"name": " Community"
"agentLanguage": "en",
"status": "ASSIGNED",
"assignedTime": "2021-10-01T10:13:11.695Z",
"xmpp": "user_1624003758958"

While raising a ticket, you can pass fields such as Name , Contact (Email/Phone Number), and Query. Message after ticket assignment will be seen by the user on getting connected to the agent.

Advanced options#

To provide additional information to the ticket.

As configured in Inbox Settings, Tags and Custom Fields will be visible in a multi-select dropdown(i.e. more than one options can be added to ticket)

  • Tags - Selected Tags from dropdown will be added to the extra details of the ticket (useful for agents to get a quick overview of the issue).
  • Department - Similar tickets can be assigned to relevant departments.
  • Priority - Denotes the priority of tickets from high, medium or low. (default priority is MEDIUM)
  • Voice Call Options - Voice Call, SIP Call and Auto Start Call can be enabled.
  • Custom Fields - Based on the use case additional information collected by bot can be added to ticket. for example, in eCommerce Order ID, Payment Mode, Delivery date etc can be asked before connecting to the agent. Just like key value pairs, once a custom field is selected, an additional prompt will be seen.

Error handling#

Output of Raise Ticket Node dictates general behaviour for any error in creating a ticket. In most real life scenarios, it is preferred to show appropriate reasons to users as to why they cannot to an agent.


Once any specific event is active and configured, the corresponding flow will be given preference. Bot is never paused unless a ticket is in ASSIGNED state (i.e. Agent is interacting with the user).

Two steps to handle custom scenarios are as follows:

  1. In Event Hub, activate the custom inbox event. Scenarios that can be handled:
  • All Available Agents Busy
  • All Available Agents Away
  • All Available Agents Offline
  • All Available Agents Limit Reached
  • Queue Not Enabled
  • Group Queue Not Enabled
  • Group Queue Limit Reached
  • Offline Ticketing Not Enabled
  • Offline Ticketing Not Enabled for Groups
  • Offline Ticket Queue Limit Reached
  1. Build a Flow with relevant events added in the Start Trigger.

Working hours#

If the bot is supposed to respond with a different message outside of agent working hours, Logic Node can be used.


The bot default timezone is considered while evaluating whether a user is outside working hours.

Inbox support auto translate feature out of the box so agents don't need to know the customer's language in order to help them. Just enable Translate User Message in the raise ticket node configuration to use this feature.


1.8 Analytics#

Capture analytics with this node.

The analytics node can be used to send analytics events and capture custom events at any point in the execution of a flow. You can type the event name to push and select a value. The data passed via the node will flow into the analytics table of Data Explorer inside the Insights section.

Event - This can be a static name or a variable which will be captured under the Events column on the analytics table.

Value - A variable needs to be selected here which will be captured under the eventValue column.

Keys - This is an optional field to capture metadata and will be created as a new column. Multiple columns can be created using keys.

Pro-tip: Using custom events, you can analyse user flow from one flow/step to another, filter by specific custom events, summarise by different user responses, visualise drop offs and conversion funnels, etc.

Open the Analytics page by clicking the Analytics Table link.

1.9 Generate PDF/Image#

Generate PDF/JPG/JPEG/PNG files having dynamic details with this node.

Steps to generate dynamic documents:

  1. Upload a template document: This document should be in .docx format and have placeholder values wherever the dynamic data is to be inserted. The placeholder should be enclosed in single brackets, that is{placeholdername}. For example, The company name is {company name}.
  2. Map placeholder names to variables: Enter the placeholder name without the brackets in the left column and select a variable value in the right column.
  3. Save to a variable: This can now be sent through the Send file node. Simply choose the relevant variable from the fetch from variable dropdown, it will send the dynamically generated file as a PDF to the user.

1.10 Data formatter#

Convert data from CSV to JSON with this node. you can ask and store the CSV data in any variable and change it to JSON using the data formatter node. The formatted value can be stored in a variable of type array or object and be displayed using another node.

1.11 Payment#

(Currently unavailable.)

Generate a payment link with this node.

1.12 Switch flow#

(Currently unavailable.)

Quit the current flow and launch another flow with this node. Here, flow switches to another flow from that point (one cannot have any nodes post this).

2. Code based nodes#

2.1 API#

This node is available for voice bots.

API action node allows you to hit an API at that point of the flow, assign dynamic API parameters (if any) from user inputs and then store API response in a variable for further use.

In the above node, we selected an API (explore_car) to hit, and we provided value to the parameter using a variable. Then we store the whole response we will get from that API in a variable.


(Optional field)

Sometimes, an API response can be too big, or not in a proper format for us to be able to parse easily. (A function is not needed just to access a simple field of a JSON API response). In those cases, we can write a function to parse and transform API response according to our needs and return desirable response.

Snippet for function#

return new Promise
(resolve => {
// For transfromation function tagged in API Node, To fetch api response
const response = ymLib.args.apiResponse;
// Your logic here
// Any value returned (or promisified value) - is stored in bot Variable storing API response
return resolve(<parsed response>);

To be able to invoke an API at a certain point, it should already be added/configured at the API management section of the platform. All APIs added there are available in dropdown of the action node. Click here to learn how to add APIs.

2.2 Variables#

This node is available for voice bots.

Store response in option available in most of the nodes are used to store variable values, Variable node is used for specific logical usecases when you want to manipulate just a variable value or skip particular steps but not do any further actions. Set the value of one or more variables with this node.

Select the following:

  • Name: Logic driven variable whose value you would like to change in this flow.
  • Value: Existing variable that hold some value (if the value is blank, it will be set to an empty string).

Learn how to create a variable here.

Use case

  1. Variable node to store InitialCounterValue: In a flow that records if a bot user is answering all the questions and reaching the end of the flow, at the start of the flow, InitialCounterValue is set to 0 (False) and when the user completes the flow the InitialCounterValue will change to 1 (True). If the flow is not completed (InitialCounterValue=0), a notification can be sent to user asking them to complete the flow.
  2. Variable node can be used to store values that are not recorded by other nodes: To obtain bot users phone number on a a web bot, you must use a Phone node/question node to pose a question and obtain the phone number, but while using the same on WhatsApp bot, the number can be fetched from the user profile. In this case, Phone Variable can be set to Phone- User Properties variable (which gets fetched automatically in WhatsApp bots).

2.3 Database#

This node is available for voice bots.

Database action node helps you in performing simple insert, update and search operations on your database tables.

1. Insert#

You select the insert operation to insert details in each column into any existing database table you select.

You can collect the entered information and store it in the new record (by adding a new record to the existing database table).

2. Search#

You can perform the search operation for database node.

  1. Select Table: For searching, you can select a table you want to perform a search on.
  2. Add filter: You can also add filters to your search.
  3. Sort Response: Sort the entered information.


Each of the following filter conditions are explained for the use-case when the user enters a date : 15/aug/2022

  • Is : searches for the exact match. Eg: To search how many times 15/aug/2022 is entered.

  • Contains : This will be matched if it contains the given value. Eg: contains 08 (august), any date with 08 will be searched 10/aug/2022, 25/aug/2005, so on.

  • Does not contain: This will be matched if it does not contain the given value. Eg: Does not contain aug/2022, all the available dates that are not from August 2022 will be searched.

  • Range: In range you can enter a from and to value as a filter. Eg: date from:'10' to: '20'.

And/Or filter#
  • You can add another filter which compares both the filter with and/or condition.
  • And: Search will display results only when both the filters are true.
  • Or: Search will display results if either of the filters holds true.

  1. Output : You can sort the output based on a string type column (optional), modify the size of output (maximum no. of records to fetch) and store this result in a variable.
Sort response#
  • Select the column name you want to sort and click ASC/DEC (this will sort the info in the table in ascending/descending order based on that column).

More options#
  • Filter distinct : Select a column on which distinct must be performed (this removes all the duplicate records when retrieving the records from a table).
  • Pagination :Page number and Size limit can be set here.

3. Update#

Update option in the database node can be used to update values stored in the tables following the given steps:

  1. Select update option in database node.
  2. Select the name of the table.
  3. You can add a where condition that acts as condition that has to be met in order to update the value.
  4. In Update with :
  • In Fields add the name of column.
  • In with value add the variable storing the value that you want to update current.

2.4 Function#

This node is available for voice bots.

Execute custom code written for a function with this node. In this node, you can select the function you wish to execute and variable to store the return value of a function (optional).

2.5 Modifier#

Modify input variable or text to lowercase, capitalize, remove from the end, replace with’ and store the modified value using this node. This node can be used when you want to modify some user input before entering them to a Database or pass them to an API node, or fetch from API and show them to user etc.

You can also test your series of modifiers by entering different input strings to check whether you are getting the desired output in the test window shown below.

2.6 Connect TransXT#

(This node is Currently unavailable.)

Connect TransXT function with this node.

3. Nodes for language & notification#

3.1 Set language#

Change the bot language to any of the configured languages using this node.

Set language action node takes only one input - variable containing ISO code of language you wish to change to. Arrange the nodes as follows:

  • Configure a node to ask for a valid ISO code (only languages configured with the bot are allowed) and store the value in the variable. You can use a question node for this. Click here for the list of languages that we support.
  • Connect the Set Language node to the node that takes ISO input. Select the variable in which the previous reply is stored. This language will be permanently set (currently set 2 days of expiry), unless it is being changed by same action node only.


Language can only be changed to only if that language is configured in bot settings, otherwise, the node will fail.

Notification Nodes (Outbound Notification, Notification Status and Voice Call) are currently not in use. Coming soon!

3.2 Outbound notification#

Send outbound SMS, email, WhatsApp, and voice notification with this node. To know more, See Outbound notifications or Workflow campaigns.

3.3 Notification status#

Check outbound notification status with this node.

3.4 Voice call#

Make voice calls with this node.

4. Workflow nodes#


These nodes are only available when a flow is created as a workflow.

4.1 Sync database#

This node enables bulk operations like "Import, Insert, Update" on tables (of bigger databases) from external data sources through APIs instead of updating them manually. You can also schedule database updates.


To setup a sync database node, follow the steps below:

  1. Create a Schedule Event (if there is a requirement to schedule the database updates).

  1. Create an API. Create a table in the required format (template without any rows).

  1. Create/open a workflow. On the start node, select the scheduled event as the start trigger.

  1. Connect the start node to the Sync Database node.
  2. Select the API, Table and appropriate action.
    • Insert: Adds rows from API call to the end of the table.
    • Update: Compares rows from API call to the existing table and checks if there is a match in Unique ID and updates those rows.
    • Import: Truncates existing table completely and replaces it with data from API call.

  1. When this is triggered, the node pulls all the data through API.
  • Data is supported only in CSV format.
  • There is no restriction on the file size.
  • All the rows will be imported, processed and sent to the selected table to perform the selected action.


  1. Configure a parser function where individual row attributes could be accessed with a custom code:
return new Promise(resolve => {
let record = ymLib.args.record;
record is an object, representing a row. all values will be of type string, keys will be fetched from the csv-header.
identifier: record.identifier,
category: record.category
  1. On the scheduled time, status of the sync can be viewed in "status" object.
success: true,
error : 'if any, we show it',
recordsProcessed: 1230,