Building a Custom AI Knowledge Assistant! 🚀 I’ve been experimenting with n8n and Google Gemini t...

Building a Custom AI Knowledge Assistant! 🚀 I’ve been experimenting with n8n and Google Gemini t...Building a Custom AI Knowledge Assistant! 🚀 I’ve been experimenting with n8n and Google Gemini t...

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

Aasma Aziz

• Aug 13

Building a Custom AI Knowledge Assistant! 🚀

I’ve been experimenting with n8n and Google Gemini to build intelligent, context-aware chatbots. Here’s a sneak peek at a prototype I built for a clinic site!

💡 What it does:

Instant knowledge retrieval for specific queries like clinic timings and break schedules Doctor's and clinic's information, directly from system context.

Fast execution time (< 4 seconds response)!

🔮 Next Step: Adding custom tools to execute real-time action triggers (like appointment bookings via Calendly API).

Always learning and iterating! Would love to hear thoughts or feedback from the automation community. 🤖✨

#BuildInPublic #AIAgents #n8n

#WorkflowAutomation #NoCode #AIAssistant

N8N healthtech AI Agent Development

Olubade Esther

pro

• Aug 24

Let’s Settle the Debate: Gemini vs. ChatGPT

Pulling back the curtain on my design workflow! To show how different AI tools interpret marketing prompts, I put two of the biggest platforms head-to-head.

I used the exact same prompt for both, but the differences in color, depth, and overall composition are massive. Take a close look at the details, textures, and lighting

which tool wins the ultimate ad test?

Cast your vote below

ChatGPT ads gemini

8 voted

25%

24 voted

75%

32 votes

Closed

Sekinat Akinrinde

• Aug 24

i'll go for chatgpt

Sebastian Avelar

pro

• Aug 24

Hey! I just shared a write-up on something I learned while rebuilding a product with AI agents:)

The main idea is pretty simple: Don’t put all your product context in one giant agent file.

Keep the main file small, and put the real product knowledge inside structured docs that the AI can navigate when it needs them.

This has helped me a lot when working on a SaaS product with a lot of business logic!

Sharing the full breakdown here:

https://docswarp.notion.site/How-to-document-your-product-so-AI-can-actually-build-it-3c09678204c580948a52c0f4ec86d6fc?source=copy_link

I'm offering consulting services to set this up! :)

Claude GitHub Supabase AI Engineer AI Development Product Design

Mark Barliet

pro

• Aug 25

The table-of-contents-in-the-main-file pattern is the key move here - it keeps the agent's default context small while still giving it a map to go fetch the architecture or naming-convention doc only when the task actually touches that domain.