This rantir workflow demonstrates how to manage your Qdrant vector store when there is a need to keep it in sync with local files. It covers creating, updating, and deleting vector store records, ensuring that your chatbot assistant is never outdated or misleading.
Disclaimer
This workflow depends on local files accessed through the local filesystem and will only work on a self-hosted version of rantir at this time. It is possible to amend this workflow to work on rantir cloud by replacing the local file trigger and read file nodes.
How it works
- A local directory, where bank statements are downloaded, is monitored via a local file trigger. The trigger watches for file create, file changed, and file deleted events.
- When a file is created, its contents are uploaded to the vector store.
- When a file is updated, its previous records are replaced.
- When the file is deleted, the corresponding records are also removed from the vector store.
- A simple Question and Answer Chatbot is set up to answer any questions about the bank statements in the system.
Requirements
- A self-hosted version of rantir. Some of the nodes used in this workflow only work with the local filesystem.
- Qdrant instance to store the records.
Customising the workflow
This workflow can also work with remote data. Try integrating accounting or CRM software to build a managed system for payroll, invoices, and more.
Want to go fully local?
A version of this workflow is available which uses Ollama instead. You can download this template here: https://drive.google.com/file/d/189F1fNOiw6naNSlSwnyLVEm_Ho_IFfdM/view?usp=sharing
Other Workflows like this one
Your connected stack awaits to automate AI workflows with 24-7 uptime performance and engagement