According to Qdrant guidelines, using the same identifier should update the existing point rather than creating a duplicate. However, in n8n there doesn’t seem to be a direct way to assign a unique ID to a Qdrant point. I attempted to set an ID within the metadata, but it does not function as the point’s actual identifier, which results in duplicate entries whenever the document is inserted. How can I properly configure a custom ID for Qdrant points in n8n?
hey guys i solved this by post-procssing duplicate points since n8n doesn’t allow custom id assignment. not ideal but raising a feature req with n8n might help eventually.
Based on my experience, n8n currently doesn’t provide a native way to use a custom ID as a Qdrant point identifier. To circumvent this, I developed a workflow that first checks if a point already exists in Qdrant by querying based on your unique field. If a match is found, the workflow then updates that point rather than inserting a new one. This method involves some additional steps but effectively prevents duplicate entries. Although it isn’t as clean as having direct support, it has been a reliable workaround for my use case.
I encountered a similar scenario while integrating Qdrant with n8n. In my implementation, I decided to build a two-step workflow where upon receiving new data, the system first performs a lookup to determine if the unique value from my intended custom ID exists. If it does, the process updates the existing entry. Otherwise, a new point is added to Qdrant. Although this method involves an extra verification phase, it has worked reliably for preventing duplicates, and until n8n offers support for custom IDs directly, it remains a practical solution.