I built an n8n workflow that shows a simple way to use multiple, specialized knowledge bases.
Imagine you manage three vacation rental properties. A guest at one of your properties texts asking how to turn on the heat, but you accidentally send them instructions for your other property’s completely different thermostat. You look unprofessional, your guest is confused, and now they are cold.
To handle this, we can use multiple, specialized Pinecone Assistants in an n8n workflow.
Here’s how it works:
-
Guest sends a question via text/email
-
Router identifies which property they’re asking about
-
Query gets routed to that property’s dedicated assistant
-
Assistant retrieves the answer from that property’s knowledge base (house manual, appliance guides, local recs, WiFi codes)
-
Guest gets the RIGHT answer for THEIR property
Each property has its own Pinecone Assistant node with its own knowledge base. No mixing. No confusion. No wrong answers.
You need separate assistants when knowledge bases can’t be combined:
-
Multiple vacation properties (different rules, amenities, locations)
-
Multi-location franchises (different staff, vendors, local procedures)
-
Agency managing multiple clients (confidential, distinct brand voices)
-
Any scenario where “close enough” isn’t good enough
You can use this full workflow template and adapt this pattern for your own use case: Handle guest inquiries for multiple rentals with Pinecone Assistant and GPT-4.1 | n8n workflow template
What would you build with this?