Qdrant icon

Qdrant

Official n8n node to interface with Qdrant - https://qdrant.tech

Actions26

Overview

The node provides an interface to Qdrant, a vector search engine and database. Specifically, the Overwrite Payload operation under the Payload resource allows users to replace existing payload data for selected points within a specified collection. This is useful when you want to update or reset metadata associated with points in a collection, such as tags, labels, or other custom attributes.

Typical use cases include:

  • Resetting or updating metadata for specific points after reprocessing or reclassification.
  • Bulk overwriting of payload data based on filters or explicit point IDs.
  • Managing and maintaining up-to-date contextual information attached to vectors in a collection.

For example, if you have a collection of image feature vectors and want to overwrite the "category" field in the payload for certain images, this operation lets you do that efficiently.

Properties

Name Meaning
Collection Name The target collection where points reside. You can select from an existing list of collections or specify the collection name directly.
Payload The new payload data (in JSON format) that will overwrite the existing payload values for the selected points.
Point IDs A JSON array specifying explicit point IDs to select for payload overwrite. If omitted, selection can be done via filter criteria.
Filter A JSON object defining conditions to filter points. Only points satisfying these conditions will have their payload overwritten.
Key A string path indicating where in each point's payload the new payload should be assigned. For example, specifying a nested property path.
Shard Key JSON value specifying which shards to look into for points. If not provided, all shards are searched. Useful for distributed collections.
Wait Boolean flag indicating whether the operation should wait until changes are fully applied before returning.
Ordering Defines ordering guarantees for the operation. Options are: Weak, Medium, Strong — controlling consistency and ordering semantics during the overwrite process.

Output

The node outputs JSON data representing the result of the overwrite operation. This typically includes status information about the success or failure of the operation, and may contain details such as the number of points affected.

If binary data output is supported by other operations, it is not relevant here since this operation deals exclusively with JSON payloads.

Dependencies

  • Requires connection to a Qdrant instance via its REST API.
  • An API key or authentication token credential must be configured in n8n to authorize requests.
  • The base URL of the Qdrant service must be set in the node credentials.
  • No additional external dependencies beyond the Qdrant REST API.

Troubleshooting

  • Common issues:

    • Incorrect collection name or non-existent collection will cause errors.
    • Malformed JSON in the Payload, Filter, Point IDs, or Shard Key fields can lead to request failures.
    • Specifying invalid point IDs or filters that match no points results in no changes.
    • Network or authentication errors if the Qdrant endpoint or credentials are misconfigured.

  • Error messages and resolutions:

    • "Collection not found": Verify the collection name is correct and exists in Qdrant.
    • "Invalid JSON format": Check the syntax of JSON inputs like Payload or Filter.
    • "Unauthorized" or "Authentication failed": Confirm API credentials are valid and properly set.
    • "Shard key not found": Ensure shard keys specified exist in the collection configuration.

Links and References

Discussion