Qdrant icon

Qdrant

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

Actions26

Overview

The node interfaces with Qdrant, a vector search engine, to manipulate data points within collections. Specifically, the Set Payload operation allows users to update or set custom payload data on selected points in a collection. This is useful for enriching points with metadata or additional attributes that can be used later for filtering, searching, or grouping.

Common scenarios include:

  • Adding tags or categories to points after they have been inserted.
  • Updating metadata fields such as status, labels, or timestamps.
  • Setting nested payload values at specific keys within each point's payload.

For example, you might use this node to assign a "processed" flag to a batch of points after running an analysis, or to add user-defined labels to points matching certain criteria.

Properties

Name Meaning
Collection Name The name of the collection where the points reside.
Payload JSON object representing the payload values to set on the points.
Points JSON array of point IDs to which the payload should be applied.
Filter JSON object defining conditions to select only points that satisfy these criteria.
Key A string path specifying where in the point's payload the new payload should be assigned.
Shard Key JSON value specifying which shards to search for points; if omitted, all shards are searched.
Wait Boolean indicating whether to wait until the changes are confirmed before proceeding.
Ordering Defines ordering guarantees for the operation; options are: Weak, Medium, Strong.

Output

The node outputs JSON data reflecting the result of the payload setting operation. Typically, this includes confirmation of success and possibly details about the updated points. If binary data were involved (not indicated here), it would represent raw data associated with points.

Dependencies

  • Requires connection to a Qdrant instance via an API URL and an API key credential.
  • The node expects proper authentication credentials configured in n8n to communicate with the Qdrant service.

Troubleshooting

  • Common issues:

    • Incorrect collection name or non-existent collection will cause errors.
    • Malformed JSON in Payload, Points, Filter, or Shard Key properties may lead to request failures.
    • Specifying points or filters that do not match any existing points results in no updates.
    • Network or authentication errors if API credentials are missing or invalid.

  • Error messages:

    • Errors related to authorization typically indicate missing or incorrect API credentials.
    • Validation errors often arise from invalid JSON input or unsupported property values.
    • Timeout or connectivity errors suggest network issues or unreachable Qdrant endpoint.

To resolve these, verify collection existence, ensure JSON inputs are valid, confirm API credentials, and check network connectivity.

Links and References

Discussion