Knowledge Bases can be integrated into workflows to enable AI agents to query them for contextual information when generating responses.
Not available in v5.4: Workflow-based content ingestion (adding, updating, or deleting Knowledge Base content from workflows) is planned for a future release. Currently, you can only upload content manually through the Knowledge Base interface.
When using the ReAct (Reasoning and Acting) model, the agent can:
Reason: Determine if Knowledge Base information is needed
Act: Query the Knowledge Base as a tool
Iterate: Make multiple queries if needed for comprehensive answers
Example ReAct flow:
Report incorrect code
Copy
Ask AI
User: "What are the new features in version 2.5?"Agent Reasoning: I need to search the Knowledge Base for version 2.5 informationAgent Action: Query Knowledge Base with "new features version 2.5"Knowledge Base: Returns 3 relevant chunks about version 2.5 featuresAgent Reasoning: I have enough information to answer the questionAgent Response: "Version 2.5 introduces three major features..."
Workflow: Weekly Knowledge UpdateNodes: 1. Fetch from CRM System 2. Append to KB - Content Source: "CRM Updates" 3. Fetch from Documentation Site 4. Append to KB - Content Source: "Documentation" 5. Fetch from Support Tickets 6. Append to KB - Content Source: "Support Insights"
Error:Content source "Example" does not exist in Knowledge Base "KB Name"Cause: Attempting to append or replace content in a non-existent content sourceSolution:
Verify the content source name is correct
Use “Append Content” which creates the content source if it doesn’t exist
Check for typos in content source names
Invalid JSON content
Error:Failed to parse JSON contentCause: The content provided is not valid JSONSolution:
Ensure workflow variables contain valid JSON
Validate JSON structure before passing to Knowledge Base operation
Check for special characters that may break JSON formatting
Knowledge Base not accessible
Error:Knowledge Base "KB Name" not found or not accessibleCause: The Knowledge Base doesn’t exist or you don’t have permissionsSolution:
Verify the Knowledge Base exists in the project or dependencies
Check access permissions for the Knowledge Base
Ensure the Knowledge Base is published if using from dependencies
Chunking failed
Error:Failed to process content into chunksCause: Error occurred while creating chunks from the contentSolution:
Chunk size matters: If chunks are too large and queries are small, relevance scores will be low because the query doesn’t cover all the content. If you find yourself setting minimum relevance score to 0%, this may indicate your chunks are too large.
Let the agent determine relevance: Consider ordering chunks by relevance (descending) and letting the agent evaluate which chunks are relevant, rather than filtering by minimum relevance score. The agent can see if chunks are relevant and make better decisions.
System prompt guidance: If you want to manage relevance filtering, add instructions to your system prompt such as: “If you don’t find any relevant information in the provided chunks, just say ‘I cannot find this information’.”
Empty results handling: The Knowledge Base tool returns an empty list when no results are found. Ensure your agent handles empty results gracefully and informs users when information is not available.
Keep content sources focused and organized by topic
Use content source filters when you know which source contains relevant information
Avoid ingesting extremely large documents without proper structuring
Regular cleanup of deprecated content sources
Consider removing max results limit: Instead of limiting the number of chunks, order them by relevance (descending) and let the agent process all relevant chunks. This allows the agent to make better decisions about which information to use.
