Qdrant

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

Actions26

Collection Actions
Payload Actions
Point Actions
Search Actions
Vector Actions
- Update Vectors
- Delete Vectors

Overview

The node provides an interface to interact with Qdrant, a vector search engine. Specifically, the Clear Payload operation under the Payload resource allows users to remove or clear payload data associated with points in a specified collection. This is useful when you want to reset or clean metadata attached to vectors without deleting the vectors themselves.

Common scenarios include:

Removing outdated or incorrect metadata from selected points.
Cleaning up payloads before reassigning new metadata.
Managing and maintaining the quality of stored vector data by clearing unnecessary payload information.

For example, if you have a collection of image feature vectors with tags as payload, and some tags are no longer relevant, you can clear those payloads selectively based on point IDs or filters.

Properties

Name	Meaning
Collection Name	The name of the collection where the points reside. You can select it from a list of existing collections or specify it by name.
Point IDs	A JSON array specifying the exact point IDs whose payloads should be cleared. If omitted, other selection criteria apply.
Filter	A JSON object defining conditions to select points whose payloads will be cleared. Only points matching this filter will be affected.
Shard Key	A JSON value specifying which shards to target for the operation. If not provided, the operation applies across all shards.
Wait	Boolean flag indicating whether the node should wait for the changes to be fully applied before proceeding. Defaults to true.
Ordering	Defines the ordering guarantees for the operation. Options are: - Weak - Medium - Strong This controls consistency and ordering behavior during the payload clearing process.

Output

The node outputs JSON data representing the result of the clear payload operation. Typically, this includes status information about the operation's success or failure, and possibly metadata about how many points were affected.

If the node supports binary data output (not indicated here), it would represent any binary payloads returned by the API, but for this operation, the output is primarily JSON confirming the clearing action.

Dependencies

Requires connection to a Qdrant instance via its REST API.
Needs an API key or authentication token configured in n8n credentials 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: Ensure the collection exists and is spelled correctly.
- Invalid point IDs or filter syntax: Verify JSON formatting and that point IDs exist in the collection.
- Insufficient permissions: Confirm the API key has rights to modify payloads.
- Network or connectivity problems to the Qdrant server.
Error messages:
- "Collection not found": Check the collection name and existence.
- "Invalid filter format": Validate the JSON structure of the filter property.
- "Unauthorized" or "Authentication failed": Verify API credentials.
- Timeout errors: Consider setting Wait to false or check network stability.

Resolving these typically involves verifying input parameters, credentials, and network access.