Is knowledge base management through VAPI's GUI ev...
# support
g
In January you were able to upload files on the website (
Build
->
Files
), plug that file/knowledge base into an assistant (
Select an assistant
->
Knowledge Base Dropdown
->
Select the file you added
) and the assistant would use that as the knowledge base. I didn't have to interact with treive or anything outside of VAPI to do this. Is that feature ever going to be fixed? Or did it get done away with?
v
The feature for uploading files directly to the knowledge base in VAPI has been temporarily removed due to the transition to the new Trieve system. Previously, users could upload files through the VAPI interface, but now the process requires using API calls instead. While the direct UI interaction for uploading files is not available at the moment, VAPI plans to restore this capability once the dashboard updates are complete. So, it hasn't been permanently removed; it's just undergoing changes. In the meantime, you can still upload files using the API, which supports various formats like Markdown, PDF, and Word documents. If you need help with the API process or have any other questions, feel free to ask! 😊 Sources: - [Report on VAPI's Feature for Uploading Files as a Knowledge Base](https://discord.com/channels/1211482211119796234/1211483291191083018/1340866019966718034) - [Detailed Report on Knowledge Base Functionality Updates for VAPI](https://discord.com/channels/1211482211119796234/1211483291191083018/1336371356731834459)
g
When is it going to be fixed? I have non devs on my team who need to be able to adjust files in the knowledge base.
m
By the end of the quarter when dashboard v2 comes out is what I’ve heard
l
For what it's worth, Trieve has a pretty good UI and non devs will be able to navigate it and upload files, etc. There are a lot of other benefits by using Trieve directly as well. You just hook up your API Key to Provider Credentials and it works well within Vapi
g
I’ve got it hooked up I just can’t get my agent to use it correctly.
s
@ghughes13 @LLMUser995 @Mason | Building KOI At this time, we sincerely apologize for your previous experience. Rest assured that we are actively working on developing a comprehensive and permanent solution to this issue.