AI agent knowledge
In this article, you'll learn how knowledge sources work in Enjo, how to add and manage them for your AI Agent, and which integrations are supported.
How knowledge works
Each AI Agent is grounded in one or more knowledge sources. When a user asks a question, the AI Agent searches connected knowledge sources, generates a response based on the most relevant content, and includes citations with links back to the source.
Knowledge sources can contain pages, documents, articles, or tickets from a connected app. A single knowledge source can span multiple folders, spaces, or categories within that app.
Global vs agent-specific knowledge
Global knowledge sources are managed centrally and can be shared across multiple AI Agents. Configure these from the Global Knowledge page in your workspace settings. This is useful when multiple agents need access to the same content โ for example, a company-wide policy document.
Agent-specific knowledge sources are configured directly on an individual AI Agent and are only available to that agent. Use these when an agent needs access to specialized or team-specific content.
๐ก Start with global knowledge sources for content that applies across your organisation. Use agent-specific sources to layer in content that is only relevant to a particular team or use case.
Add a knowledge source
Go to AI Agents and select the agent you want to configure.
Open the Knowledge tab.
Click Add Knowledge.
Select the app or source type from the drawer.
Follow the setup steps for your selected source. See the integration guides below.
Preferred knowledge sources
You can set a preference order for knowledge sources on an AI Agent. When multiple sources contain relevant content, the AI Agent prioritizes sources higher in the preference order.
Supported knowledge sources
Source | Description |
|---|---|
Wiki pages and documentation from Atlassian Confluence. | |
Documents and files from Google Workspace. Synced daily. | |
Documents and pages from Microsoft 365. S | |
Past conversations from Microsoft Teams channels. | |
Pages and databases from Notion. | |
Past tickets from Jira. | |
Past tickets from Zendesk. | |
Knowledge Base articles from Salesforce. | |
Past cases from Salesforce Service Cloud. | |
Knowledge Base articles from ServiceNow. | |
Work items and tasks from Azure DevOps. Indexed via WIQL queries. | |
PDF, DOCX, and other files uploaded directly to Enjo. | |
Content from your website or external URLs is crawled and indexed. | |
Past conversations from Slack channels. | |
Zammad | Past tickets from Zammad. |
Bitbucket | Past issues from Bitbucket. |
๐ก The integration surface expands continuously. If a source you need is not listed, contact the Enjo support team.
What's next
Guidelines for Knowledgeโ Manage shared knowledge sources across your workspace.
Confluence as Knowledge โ Ground your AI Agent in your confluence
Notion as Knowledge โ Validate AI responses across your knowledge sources at scale.
