Node types + setup

Get acquainted with all nodes types and how to use them in NLX's Dialog Studio

Node side panel

Clicking any node on your Canvas reveals a side panel to display information about the selected node and provide options for adding or refining its actions. Clicking outside of the node automatically closes its side panel.

Nodes overview

Get quickly acquainted with the variety of nodes available in the Canvas builder:

Every node has a non-editable ID that's auto-generated so the node can be referenced across Dialog Studio. To show or hide the Node ID, click the info icon in the upper right of the node's side panel.


Start node is the home node of every flow. It's non-editable, provides information on how the flow is reached by users, and should be attached to the first node added to the Canvas.

  • Every flow or page created within a flow automatically populates a Start node as a beginning point. A node added to the Canvas can then be attached to Start through a connector line or stacking.


Action nodes initiate an external task outside of Dialog Studio to occur.

Use of this node requires setting up an Action in your workspace.

  • An email or text sent to the user for a survey, confirmation, or set of instructions

  • Triggering the creation of a service ticket, work order, purchase, etc.

  • Scheduling an appointment or calendar meeting


Basic nodes are the easiest to include in any part of the flow. They can act as a messaging node, a processing node when given added functionality, or both.

  • Indicate via message that a process is about to occur before continuing the flow to an Action, Data request, or Escalation

  • Offer a greeting or confirmation before/after a question or capture step

  • Clear a user's input in a retry cycle

Bot handoff

Bot handoff nodes allow you to route users to a different bot and bot communication channel that exist in the same workspace.

  • Move a user from a bot handling HR questions to a bot handling an IT request

  • Move a user from one communication channel to another that's only supported by the other bot

  • Route a percentage of users via a Split node if doing A/B testing with a new bot

Data request

Data request nodes allow you to trigger information to be received during a conversation through static data or external webhook/API. They're particularly valuable when needing to relay information to a user through other nodes where the info is dynamic.

Use of this node requires setting up a Data request in your workspace.

  • Checking available rooms to assist with a hotel reservation

  • Pulling a list of local restaurants to match a user's criteria

  • Fetching the user's profile to authenticate and customize the conversation

  • A payload of information sent to a database for storage or updating (e.g., user profiles, passwords, etc.).


Define nodes allow you to define and set ephemeral values for use in a single intent flow. In essence, they work identically to Context attributes but are localized to a single flow and not retained thereafter.

  • A value captured in an intent that shouldn't be retained outside of the current flow

  • A value captured from the user must carry a different meaning in other intents in the same conversation session

  • Parsing date to extract its component parts (minutes, seconds, hours, days, etc.)


Escalate nodes immediately initiate the escalation transfer for the flow's communication channel.

Use of this node requires an escalation channel set up in your workspace Settings.

  • Business procedure requires that a user change their registered email with an agent only

  • A bot is not yet enabled with the ability to perform a task requested by the user

  • Technical processes involving APIs/webhooks fail

Generative text

Generative text nodes allow you to employ a large language model (LLM) to handle the conversation workload, including formulating responses appropriate to the context of the conversation.

Use of this node requires a one-time LLM integration in your workspace Settings

  • Carry open-ended conversations between users and a bot

  • Handle unexpected user responses

  • Link from No match connectors on previous nodes to manage unknown user responses


Loop nodes help to either set an allowed number of retries for a user's response or an API call (such as with a Data request or Action), or they can help survey items in a data array.

Range mode

  • Prevent infinite looping by allowing three retries for a user to provide their PIN before escalating to an agent

List mode

  • Loop over a list of resorts and provide matches from a user's preference of 5-star establishments in Tokyo


Note nodes are for adding freeform text to the Canvas and do not impact the intent's conversation flow.

  • Provide instructions or explanations to a teammate about items on the flow

  • Document different node stacks or sections of a flow for organization or visual mapping

  • Enter descriptions or thoughts about areas or whole pages of a flow


Redirect nodes route users to to a different page of an intent flow or to a different intent.

  • An unregistered user that needs to complete a profile before proceeding with the main flow (redirect to a page of the flow or another intent)

  • After asking a user what they need help with (User input node) and routing them based on a matched training phrase

  • Moving a user from an intent covering booking policies at a resort to an intent that books a resort reservation


Split nodes divide users in a path flow based on condition(s) or chance distribution.

  • Conducting A/B testing on new messaging or new process and diverting a portion of user traffic to test

  • Splitting voice channel users from chat channel users to provide alternate messaging for one part of the flow

  • Sort users based on various criteria (e.g., rewards level, credit card type, negative vs positive attitude, etc.)

User choice

User choice nodes prompt users to either make a selection or provide information for a relevant action, such as routing, refining, or externally passing along the info.

Requires: Attaching a slot to the intent or setting up a Data request.

  • Ask a user for the start date of their reported service outage

  • Ask a user a Yes/No question

  • Ask a user to choose from their available credit cards on file

  • Ask a user to provide a short explanation of their complaint

User input

User input is considered a listening and capture node for collecting a user's utterance to match to an intent's training phrase or collecting a keyword(s) that alters or routes the conversation using Split node logic.

  • Asking a user what they need help with and routing them to an intent that matches a training phrase

Last updated