AI-powered business document assistant built with RAG pipeline. What it does Upload your business...

AI-powered business document assistant built with RAG pipeline. What it does Upload your business...AI-powered business document assistant built with RAG pipeline. What it does Upload your business...

The network for creativity

Join 1.25M professional creatives like you

Connect with clients, get discovered, and run your business 100% commission-free

Creatives on Contra have earned over $150M and we are just getting started

Back to feedPost

Muhammad Fayaz Khan

• 1d

AI-powered business document assistant built with RAG pipeline.

What it does Upload your business PDFs and ask questions in plain language. Get accurate answers with source citations instantly.

Tech Stack: FastAPI —> backend Chainlit —> chat UI ChromaDB —> vector database Groq (Llama 3) —> LLM HuggingFace —> embeddings Cohere Rerank —> reranking BM25 —> hybrid search

AI Chatbot Development Administrative Support Virtual Assistance Cohere Python FastAPI

Sodiq Olalekan

• Jul 28

Ever lost a customer just because you were too busy to reply on time? 😩

That's a problem most small business owners face daily messages coming in from WhatsApp, Instagram, and email, but no time to respond.

So I built a solution 💡

An automated system using n8n that works like a 24/7 assistant. The moment a message comes in, it:

Saves the customer's info to a database Sends a welcome email Sends an SMS/WhatsApp reply Alerts the owner on Telegram to follow up

All within 5 seconds. Fully automatic.

No more lost customers. No more slow replies. Just smart automation doing the work for you. 🚀

Need something like this for your business? 😍 Send me a message.

N8N Google Sheets Zapier Business Workflow Automation

Sunday Moses

• Jul 27

Your Supabase app is working… but your database is still exposed? 🔐 One mistake I see developers make is setting up authentication and forgetting about Row Level Security (RLS).

If you're using Supabase, don't just create your tables and move on.

Make sure you:

✅ Enable RLS on your tables ✅ Create policies for who can read data ✅ Create policies for who can insert or update data ✅ Never expose sensitive service keys in the frontend ✅ Test your policies with different user accounts

Authentication tells you who the user is. RLS helps control what they can access.

Have you ever had an RLS policy block something that should have worked? 👇