Understanding knowledge base types
Naturalead supports two types of knowledge bases:Internal
For proprietary content such as product documentation, pricing sheets, FAQs, and sales playbooks. Content is uploaded manually or via webhook sources.
External
For publicly available content such as website pages, blog posts, and help center articles. Content is typically ingested via sitemap crawling.
Prerequisites
Before starting, make sure you have:- A Naturalead account with an API key or dashboard access
- The
knowledge:uploadpermission (granted toowner,integrator, andai_architectroles) - Content to ingest (text documents, a website URL, or an external API endpoint)
Step 1: Create a knowledge base
Step 2: Upload documents manually
For content you already have as text (FAQs, product specs, sales scripts), upload documents directly.Documents are automatically chunked and indexed in the vector store. There is no separate indexing step required.
Step 3: Crawl a website via sitemap
For external knowledge bases, you can automatically ingest content from a website by crawling its sitemap.Step 4: Manage crawl jobs
You can pause, resume, or cancel crawl jobs at any time. Pages already processed remain in the knowledge base regardless of the action taken.Pause
Temporarily stop a running crawl. Useful if you need to reduce API load or review intermediate results.
Resume
Continue a paused crawl from where it left off. No pages are re-processed.
Cancel
Permanently stop a crawl. The job cannot be resumed after cancellation.
Step 5: Set up webhook sources for auto-updating content
Webhook sources let you automatically pull content from external APIs on a schedule. This is useful for keeping your knowledge base in sync with content that changes frequently, such as a CMS, helpdesk, or product catalog.Step 6: Attach a knowledge base to an agent
Once your knowledge base has content, attach it to an AI agent configuration so conversations can use it for RAG retrieval.When a conversation is active, the AI agent queries the attached knowledge base on each inbound message to retrieve relevant context before generating a response.
Cleanup and maintenance
Delete a document
Remove a single document from a knowledge base. The document is also removed from the vector store.Delete a knowledge base
Deleting a knowledge base removes all associated documents, crawl jobs, and webhook sources.Summary
Combine all three methods within a single knowledge base to give your AI agent the most comprehensive context for lead qualification conversations.