I’m working with n8n and trying to connect to Qdrant vector database. The problem is that I can’t figure out how to assign specific IDs to my data points when inserting them.
From what I understand about Qdrant, if you insert a point with an existing ID, it should replace the old one instead of creating duplicates. But in my n8n workflow, I don’t see any option to specify the point ID directly.
I tried putting the ID in the metadata section, but that doesn’t work as the actual point identifier. This is causing issues because every time I run my workflow with the same documents, they get added as new entries instead of updating the existing ones.
Has anyone managed to set custom point IDs when using n8n with Qdrant? What’s the correct way to configure this?
The trick’s in the node config, not the data structure. When setting up your Qdrant vector store node, look for the ‘Document ID Field’ parameter - that’s what tells n8n which field to use as the point identifier. I always add a dedicated field like ‘doc_id’ or ‘point_id’ to my data, then reference it in that setting. Skip this step and n8n just generates random IDs, which creates your duplicate problem. Make sure your source data has a consistent identifier field and map it properly in the node settings. Works like a charm for both inserts and updates.
I ran into this exact same issue with my document indexing pipeline. You need to use the Document ID field in the Qdrant node config - not the metadata section you mentioned. When you expand the node settings, look under document properties. It’s separate from content and metadata inputs. I generate consistent IDs by hashing the document content or using a unique identifier from my source data. This way, when I re-run the workflow with the same docs, Qdrant overwrites existing points instead of creating duplicates. Just make sure your ID generation is deterministic. I stick a Code node before the Qdrant insertion to create SHA-256 hashes of document content - guarantees the same doc gets the same ID every time.
hey, i had that issue too! make sure to look at the advanced settings in ur qdrant node. there should be a ‘point id’ field for ur custom id. don’t stick it in metadata, trust me on this. took me a while to find it, haha.