Hey everyone,
I’m stuck trying to get N8N and Qdrant to work together. I followed the example in the docs, but I’m getting an error. It says:
Problem in node 'Qdrant Vector Store'
400 Bad Request: Wrong input: Not existing vector name error:
I made a collection in Qdrant, but maybe I did it wrong? The docs don’t really explain how to set it up properly for N8N.
Has anyone got this working? I’d love some tips on:
- How to create a Qdrant collection that works with N8N
- What the workflow file should look like
I’ve tried looking online, but I can’t find much info. If you’ve dealt with this before, I’d really appreciate your help!
Thanks in advance!
yo, i feel ur pain with N8N and Qdrant. had similar headaches. make sure ur vector name in N8N matches EXACTLY what u set in Qdrant. double-check ur Qdrant API endpoint too. if ur still stuck, try a basic workflow with just the Qdrant node to narrow down the issue. good luck!
I’ve encountered similar issues when integrating N8N with Qdrant. The ‘Not existing vector name’ error typically stems from a mismatch between your N8N configuration and Qdrant setup.
First, double-check your Qdrant collection creation. Use the Qdrant API to explicitly define the vector name and dimensions. For example, send a POST request to /collections/{collection_name} with a body specifying the vectors object.
In your N8N workflow, ensure the Qdrant node’s vector name exactly matches what you set in Qdrant. Even minor discrepancies can trigger this error.
Verify your Qdrant API endpoint in N8N is correct. For local instances, it’s usually ‘http://localhost:6333’.
If issues persist, create a minimal N8N workflow with just the Qdrant node for testing. This can help isolate the problem and provide more specific error messages for troubleshooting.
I’ve been through a similar situation with N8N and Qdrant, and it can be frustrating when the docs don’t cover everything. From my experience, the key is in the vector name setup.
When you create your Qdrant collection, make sure you explicitly define the vector name. You can do this through the Qdrant API with a POST request to /collections/{collection_name}. In the request body, include a ‘vectors’ object with your desired vector name and dimensions.
For the N8N workflow, double-check that the vector name in your Qdrant node matches exactly what you set up in Qdrant. Even a slight mismatch can cause that ‘Not existing vector name’ error.
Also, ensure your Qdrant API endpoint in N8N is correct. If you’re using a local instance, it should be something like ‘http://localhost:6333’.
If you’re still stuck, try creating a minimal workflow in N8N with just the Qdrant node and test different configurations. The error messages can sometimes give more clues about what’s going wrong.