Retrieving Clients by Phone number or Order ID's from Vector Store

Questions
1

Thx n8n for this amazing product : )

I’m experiencing issues retrieving phone numbers, order IDs, and names from our Pinecone v store.

O1 advised me to use meta filters with identifier JSON keys to get precise responses from Pinecone, but from what I’ve read, this feature does not exist in n8n.

Basically, this vector space tool/agent is mostly useless for us, as it finds the order/client only 10–20% of the time, no matter how big or small the chunk size or the overlap i set up.

We simply don’t get our questions answered, despite having a clean vector space structure that seem to be well split.

{
      "pageContent": "; Name: Go*** Guntaka (Kevin; Identifier: +1*******336, gu*********[email protected], 160*****08, ;",
      "metadata": {
        "blobType": "text/plain",
        "createdTime": "2024-08-21T00:46:28.000Z",
        "loc.lines.from": 47,
        "loc.lines.to": 48,
        "recordID": "recYhbg9NdT6UxMlB",
        "source": "Clients"
      },
      "id": "5d10d4de-dbb3-491e-9070-87a74a6b2b21"
    },
    {

please help🥲

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3
  • n8n version: Version 1.71.2
  • Database (default: SQLite): where to lookup?
  • n8n EXECUTIONS_PROCESS setting (default: own, main): no idea what that is
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Railway
  • Operating system:
4

Hi @prostor.dd

Thanks for posting here and welcome to the community! :raised_hands:

The Pincecone node does allow for a Metadata Filter:

image
image850×1298 53.2 KB

If you put your identifiers in the metadata column directly, you can reference this in your workflow and the retriever will be able to find the relevant data more accurately :slight_smile:

Hope this helps!

5

Thank you, overlooked it…

And I have a follow-up question: When a human requests record by by record ID, for example, the AI method does not work… a bit confused how to implement this…

CleanShot 2024-12-24 at 14.55.48@2x
CleanShot 2024-12-24 at 14.55.48@2x854×410 19.3 KB

CleanShot 2024-12-24 at 14.42.01@2x
CleanShot 2024-12-24 at 14.42.01@2x2102×646 72 KB

CleanShot 2024-12-24 at 14.43.42@2x
CleanShot 2024-12-24 at 14.43.42@2x752×310 19 KB

6

basic name fromAI also does not work, so how shout this be done?

CleanShot 2024-12-24 at 15.02.13@2x
CleanShot 2024-12-24 at 15.02.13@2x1198×560 30.6 KB

7

I would actually put that in the system message of the agent, and there you could also provide an example of what the recordID might look like.

We’ve actually just released a pretty cool tutorial on how to use the $fromAI() function in tool nodes. Maybe it can help to clarify some :slight_smile: