Knowledge Base
The Knowledge Base node allows a Workflow to answer users using information stored in a Knowledge Base.
Use this node when you want a Workflow to search your existing documents and data and provide an answer based on that content.
Add the Knowledge Base node from the Tools section of the node list.
For a simple document-based Workflow, use Start → Knowledge Base. If you need prompts, tools, memory, or Chat Canvas, use an Agent instead.
How the Knowledge Base Node Works
When a user message reaches the Knowledge Base node, it searches the selected Knowledge Base for relevant information.
The Workflow then decides whether to continue based on the Continue only if no answer is found setting.
The basic flow is:
User Message
↓
Start
↓
Knowledge Base
↓
Next Node (if configured)For example, if your Knowledge Base contains company policies and a user asks:
How many days of annual leave do employees get?
The Knowledge Base node searches the stored content and uses the relevant information to answer the question.
What the Knowledge Base Node Does
The Knowledge Base node:
- Searches the selected Knowledge Base.
- Looks for relevant information related to the user’s question.
- Uses the retrieved information to provide an answer.
- Determines whether the Workflow should continue based on the configured setting.
The Knowledge Base itself is created and trained outside the Workflow canvas. You can add files, URLs, and other supported data sources when managing the Knowledge Base.
The Knowledge Base node does not create or train a Knowledge Base. It only selects which Knowledge Base to use and controls how the Workflow continues after the search.
Add and Connect a Knowledge Base Node
To add a Knowledge Base node:
- Open the Workflow canvas.
- From the node list, find Knowledge Base under Tools.
- Add the node to the canvas.
- Connect the previous node to the Knowledge Base.
- Select the Knowledge Base you want to use.
- Optionally connect the Knowledge Base to another node.
The most common setup is:
Start → Knowledge BaseYou can also continue to another node:
Start → Knowledge Base → AgentFor example, you could use the Knowledge Base to retrieve company information first and then pass the Workflow to an Agent for additional processing.
Using Knowledge Base with Auto Orchestrator
If you have multiple Knowledge Bases and want the Workflow to automatically choose the most relevant one, use Auto Orchestrator.
Start
↓
Auto Orchestrator
├── Knowledge Base (Billing)
├── Knowledge Base (Products)
└── Knowledge Base (Policies)The Auto Orchestrator decides which Knowledge Base path should handle the user’s question.
Auto Orchestrator can connect only to Knowledge Base nodes.
Configure the Knowledge Base Node
Select the Knowledge Base node to open its configuration panel.
The configuration panel contains:
- Name
- Knowledge Bases
- Continue only if no answer is found
Select Save to apply your changes.
The Save button remains disabled until the required fields are valid.
If your organization does not have any Knowledge Bases, the panel displays No Knowledge Base Found.
Select Add Knowledge Base to create one before configuring the node.
Name
The Name identifies the Knowledge Base node on your Workflow canvas.
It is only for your reference and does not affect how the Knowledge Base searches or generates answers.
For example:
Check Customer Policiesor:
Find Product InformationThe name is required and must contain at least 3 characters.
Knowledge Bases
The Knowledge Bases field determines which Knowledge Base the node searches.
Select a Knowledge Base from the available list.
For example, if you have a Knowledge Base called Product Documentation, select it when you want this node to answer questions using your product documentation.
Each Knowledge Base can display its credits per run, depending on the selected retrieval model.
A model deprecation notice may also appear if the retrieval model is scheduled to change.
You must select a Knowledge Base before you can save the node configuration.
Continue Only If No Answer Is Found
The Continue only if no answer is found option controls what happens after the Knowledge Base search.
It is disabled by default.
| Setting | What happens |
|---|---|
| On | If no answer is found, the Workflow continues to the next node. If an answer is found, that answer is used and this path stops. |
| Off | The Workflow always continues to the next node, whether or not an answer is found. |
When to Turn It On
Turn this option On when the Knowledge Base should answer the user whenever it has a relevant answer, and another node should run only when the Knowledge Base cannot answer.
For example:
Start → Knowledge Base → AgentWith Continue only if no answer is found enabled:
- Knowledge Base finds an answer → the Knowledge Base answer is used and the path stops.
- Knowledge Base finds no answer → Workflow continues to Agent.
This is useful when you want an Agent to handle questions that are not covered by your documentation.
When to Keep It Off
Keep this option Off when you want the next node to run regardless of whether the Knowledge Base found an answer.
For example:
Start → Knowledge Base → AgentWith the option disabled, the Workflow continues to the Agent even when the Knowledge Base successfully finds an answer.
Knowledge Base Node vs Agent Knowledge Base Retrieval
Both the Knowledge Base node and the Agent’s Knowledge Base Retrieval tool can search stored content, but they are used differently.
| Knowledge Base Node | Agent Knowledge Base Retrieval | |
|---|---|---|
| Where it is configured | Directly on the Workflow canvas | Inside an Agent under Add Tool |
| Typical setup | Start → Knowledge Base | Start → Agent |
| Who controls the search | The Workflow path runs the node | The Agent decides when to use the tool |
| Best for | Simple document-based answers | Workflows that need prompts, tools, memory, or Chat Canvas |
| Can use other Agent features | No | Yes |
For example, use a Knowledge Base node when you only need to answer questions from company documentation.
Use an Agent when you need something more advanced, such as:
Start → Agent
├── Knowledge Base Retrieval
├── API Request
└── Other toolsKnowledge Base Credits
The selected Knowledge Base can display its credits per run in the configuration panel.
Credits are consumed when the Knowledge Base node runs.
If an Auto Orchestrator chooses another Knowledge Base and this node is not executed, this Knowledge Base node does not consume credits for that turn.
Knowledge Base Node Behavior
| Action | Result |
|---|---|
| Add the node without selecting a Knowledge Base | The node shows This node is not configured |
| No Knowledge Bases are available | No Knowledge Base Found is displayed |
| Select Add Knowledge Base | Opens the option to create a Knowledge Base |
| Save without a valid name | The name validation error is displayed |
| Save without selecting a Knowledge Base | The Knowledge Base validation error is displayed and Save remains disabled |
| Save a valid configuration | The node is ready to search the selected Knowledge Base |
| Continue only if no answer is found enabled | Workflow continues only when no answer is found |
| Continue only if no answer is found disabled | Workflow always continues to the next node |
| Connect from Auto Orchestrator | Allowed |
| Add multiple incoming connections | Not supported |
| Add multiple outgoing connections | Not supported |
What the Knowledge Base Node Does Not Do
The Knowledge Base node does not:
- Create or train a Knowledge Base.
- Use a system prompt.
- Add tools or memory.
- Use Chat Canvas.
- Automatically choose between multiple Knowledge Bases.
- Ask the user a question.
- Create conditional branches.
Use the appropriate Workflow node when you need these capabilities:
| Requirement | Use |
|---|---|
| Search one Knowledge Base | Knowledge Base |
| Choose between multiple Knowledge Bases | Auto Orchestrator |
| Use prompts, tools, memory, or Chat Canvas | Agent |
| Ask the user for information | User Feedback |
| Create conditional paths | If / Else |
Common Workflow Examples
Simple Knowledge Base Answer
Use this setup when all questions should be answered from one Knowledge Base.
Start → Knowledge BaseExample: A company has a Knowledge Base containing its employee handbook. Users can ask questions about company policies, leave, benefits, and other documented information.
Knowledge Base With Agent Fallback
Use this setup when you want the Knowledge Base to answer first and an Agent to handle questions when no relevant information is found.
Start → Knowledge Base → AgentEnable Continue only if no answer is found.
The behavior is:
User Question
↓
Knowledge Base
↓
Answer found? ── Yes → Use Knowledge Base answer
│
No
↓
AgentMultiple Knowledge Bases
Use Auto Orchestrator when different Knowledge Bases contain different types of information.
Start
↓
Auto Orchestrator
├── Knowledge Base (Billing)
├── Knowledge Base (Products)
└── Knowledge Base (Policies)The Auto Orchestrator determines which Knowledge Base is the best match for the user’s question.
Knowledge Base Node at a Glance
| Option | Purpose |
|---|---|
| Knowledge Base | Searches stored documents and data to answer the user’s question |
| Name | Identifies the node on the Workflow canvas |
| Knowledge Bases | Selects which Knowledge Base the node should search |
| Continue only if no answer is found | Controls whether the Workflow continues after the search |
| Save | Applies the node configuration |
| Credits / run | Shows the credits used when the selected Knowledge Base runs |
Start with a simple Start → Knowledge Base flow when you only need answers from one Knowledge Base. Use Auto Orchestrator when you need to choose between multiple Knowledge Bases, or use Agent when you need additional AI capabilities.