Workflow node types
Overview
Each step in a workflow is a node. Its type controls what the visitor sees and how the conversation moves on. Add common types from the Node Palette in Chat → Workflows, and switch a node's type with the Node Type dropdown in its configuration panel.
Every node has these fields:
- Node Name: an internal label that helps you recognize the node.
- Title (Optional) and Message: the text shown to the visitor. You can add Response Tags such as the visitor's name.
- Execution Condition: optional rules for when this node is chosen.
- Advanced Settings → Set as Start Node: marks the node where the conversation begins.
Node types in the palette
| Node | What it does | Key settings |
|---|---|---|
| Message | Shows a message, such as a greeting or information. | Message (required) |
| Question | Asks a question and shows answer buttons. Each answer can lead to a different node. | Options (option text and value), + Add Option, + Create Complete Flow, Allow user input |
| Text Input | Collects a free-text answer. | Placeholder Text, Required, Max Length, Validation Pattern (Regex) |
| Email Input | Collects an email address and checks that it's in a valid format. | Placeholder Text, Required |
| MultiSelect | Lets the visitor choose more than one option. | Options, Allow user input |
| Handoff | Shows your transfer message and hands the conversation to your team. The AI stops replying, and any team member can reply from Live monitor. | Message (required) |
| End | Shows a closing message and marks the conversation as completed. | Message (required) |
| AI Chat | Hands the conversation to one of your AI agents, which answers freely. | AI Agent (required), Knowledge Base, Context, Exit Detection |
| Book Appointment | Lets visitors pick an available time and request an appointment. This node appears only if your plan includes Calendar. | Intro message, Success message, No available times message |
Other types in the Node Type dropdown
| Node | What it does | Key settings |
|---|---|---|
| Name Input | Collects the visitor's name and saves it to the conversation. | Placeholder Text, Required, Max Length |
| Phone Input | Collects a phone number. | Placeholder Text, Required, Phone Validation Pattern |
| Number Input | Collects a number, such as 1500, 2.5 or 1,500. | Placeholder Text, Required |
| Currency Input | Collects an amount, with or without a currency symbol ($, €, £ or ¥), such as 1500 or $1,500.00. | Placeholder Text, Required |
| Date Input | Shows a date picker. | Message |
| Form Group | Shows several fields together as one form. Fields are required unless their rule says otherwise (requiredWhen). |
Form Fields: a label, a Stable key, a type (Text, Email, Phone, Number, or Date) and an optional validation rule for each field |
| Condition | Shows nothing to the visitor. It sends the conversation down one of its outgoing branches. | Set Condition Type to Orchestrator to let the AI pick the best branch |
If a visitor's answer to a Number Input or Currency Input node isn't a valid number or amount, the chat asks them to try again and stays on that step until the answer is valid.
Nodes that collect an answer (Question, the input nodes and MultiSelect) also have Stable output key and Validation rule (JSON, optional). A rule can check a range such as mileage, a model year or a US VIN, and can ask the visitor to confirm an unusually high value. Rules apply in ordinary workflows and in workflows an AI agent offers. See Field keys and validation rules.
Steps
Set up an AI Chat node
- Add an AI Chat node from the Node Palette and click it.
- Under AI Configuration, choose an AI Agent. If you don't have one yet, follow the Create an agent first link.
- Optionally, pick a Knowledge Base so the agent answers from your own documents.
- In Context, add any extra background the agent should know for this step.
- Click Save.
Let the AI move the visitor on (Exit Detection)
- In the AI Chat node, check Enable exit detection.
- Connect the AI Chat node to the nodes it may hand off to, for example a Handoff node.
- On each of those nodes, set an Execution Condition that describes when to go there.
- Optionally, fill in Exit intents (one per line, optional), Exit instructions (optional) and Min turns before exit (visitor messages required before the AI can move on).
Use execution conditions
- Open a node and find Execution Condition.
- Choose a Condition Type:
- Equals, Contains, StartsWith, EndsWith, or Regex compare against the visitor's reply.
- AI takes a plain-language description, for example "the user is asking about pricing".
- Enter the Condition Expression and click Save.
Tips
- Leave Condition Type set to No Condition unless you need branching.
- Place a Handoff node only where your team can respond. A handed-off conversation with no activity for 30 minutes is marked Abandoned.
- Personalize Success message on a Book Appointment node with {name}, {email}, and {time}.