Adding knowledge to agents

Edit online

You add knowledge so your agent can return accurate, relevant answers based on trusted information instead of relying only on the base model.

Knowledge sources provide factual and contextual data that help interpret user questions and generate meaningful responses. Without connected knowledge, responses might remain generic or incomplete, especially for domain-specific topics.

You can connect knowledge from:

  • External content repositories that update frequently.

  • Uploaded files that contain stable, reviewed information.

Before you begin

Before you configure knowledge sources, ensure that the following prerequisites are met:

  • Agents must be able to retrieve and respond by using content from external repositories in English, Spanish, French, German, and Brazilian Portuguese.

  • If you intend to use Milvus, Elasticsearch, Astra DB, or a custom service, contact your IT administrator to obtain the necessary connection details.

Choose a knowledge source

Select the type of knowledge source based on how often your content changes and how you manage it.

Use external repositories

Connect to systems such as Milvus, Elasticsearch, Astra DB, or custom services when:

  • Your content changes frequently.

  • Your content is distributed across multiple systems.

  • You need automated updates or integrations.

External repositories work well for large, dynamic datasets. For more information, see External repositories.

Use file uploads

Upload documents directly when:

  • Your content is stable and reviewed.

  • You manage content as manuals, guides, or reference documents.

  • You want fast setup without external dependencies.

Uploaded files remain part of the internal knowledge base.

These sources work alongside the agent’s built-in LLM knowledge. They add to its existing knowledge and do not replace it. For more information, see Storing your data.

Connect to an external repository

To connect your agent to an external content repository, follow the setup guide that matches the type of repository you're using:

Each guide walks you through connection configuration and validation.

Switching content repositories

You can change your agent’s content repository anytime whether switching from uploaded files to an external system like Milvus or Elasticsearch, or between external services.

Considerations before you switch

  • Existing configurations are deleted

Switching repositories deletes all previously uploaded files, indexing details, and any custom settings tied to the current knowledge source.

  • Data cannot be recovered

When deleted, the previous repository’s content and configurations cannot be restored.

  • Backup is critical

Before you switch repositories, save important files and document key settings to avoid permanent data loss.

To switch repositories:

  1. Click Change source.

  2. Select your new content repository.

  3. Confirm the action by clicking _I understand_.

Note:

This action permanently deletes the previous repository’s details and files.

What to do next