Alexandru Bagu
03/14/2025, 11:11 AMtrevie the knowledge base is working as intended.Vapi Support Bot
03/14/2025, 11:13 AMprovider field set to custom-knowledge-base. Without this, the backend won't recognize the request downstream.
Here's an example of the correct configuration:
json
{
"knowledgeBase": {
"provider": "custom-knowledge-base",
"server": {
"url": "https://your-local-server.com/knowledge-base"
}
}
}
Some troubleshooting steps you can try:
1. Verify your knowledge base provider configuration has the correct provider field
2. Check your server and API logs for any errors during requests
3. Ensure your server is properly set up to handle POST requests from Vapi
4. Verify network settings if you're running a local server
Since trevie is working for you, it suggests the issue is specific to your custom provider configuration rather than a general Vapi setup problem.
Let me know if you need more specific help with any of these steps! 🔍
Sources:
- [Discord Thread about Knowledge Base Provider](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1344182165990015016)
- [Discord Thread about Custom Knowledge Base Issues](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1340832089351782563)
- [Discord Thread about Troubleshooting](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1343853917322350703)Alexandru Bagu
03/14/2025, 11:17 AMtrieve has nothing to do with custom knowledge bases however it does point to an issue maybe in vapi's way to handle custom knowledge bases.Alexandru Bagu
03/14/2025, 11:18 AMVapi
03/15/2025, 1:28 PM