Actions26
- Delete Collection
- Get Collection
- Check Collection Exists
- Create Collection
- Update Collection
- Retrieve Point
- Retrieve Points
- Upsert Points
- Delete Points
- Update Vectors
- Delete Vectors
- Set Payload
- Overwrite Payload
- Delete Payload
- Clear Payload
- Batch Update Points
- Scroll Points
- Count Points
- Query Points
- Query Batch Points
- Query Points Groups
- Matrix Pairs
- Matrix Offsets
- Payload Facets
- Create Payload Index
- Delete Payload Index
Overview
The node provides an interface to interact with Qdrant, a vector search engine. Specifically, the "Delete Vectors" operation allows users to delete vectors from a specified collection in Qdrant. This is useful when you want to remove certain vectors either by their names or associated point IDs, optionally filtered by conditions or shard keys.
Common scenarios include:
- Cleaning up outdated or irrelevant vectors from a collection.
- Managing storage by removing unnecessary data points.
- Maintaining data accuracy by deleting vectors that no longer represent valid information.
For example, if you have a collection of image embeddings and some images are deleted or updated externally, you can use this operation to remove the corresponding vectors from Qdrant to keep the index consistent.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The name of the collection from which vectors will be deleted. |
| Vector | A JSON list specifying the names of vectors to delete. |
| Points | A JSON list of point IDs indicating which points' vectors should be deleted. |
| Filter | A JSON object defining conditions to select points for vector deletion (only points satisfying these). |
| Shard Key | A JSON value specifying shards to look into; if omitted, all shards are searched. |
| Wait | Boolean flag indicating whether to wait for the deletion changes to complete before proceeding. |
| Ordering | Defines ordering guarantees for the operation; options are Weak, Medium, or Strong consistency levels. |
Output
The node outputs JSON data representing the result of the delete vectors operation. This typically includes confirmation of the deletion request and any relevant metadata returned by the Qdrant API. There is no binary output involved.
Dependencies
- Requires connection to a Qdrant instance via its REST API.
- Needs an API key credential configured in n8n for authentication.
- The base URL for the Qdrant service must be set in the credentials.
Troubleshooting
Common issues:
- Incorrect collection name may cause errors or no action.
- Malformed JSON in vector, points, filter, or shard key fields can lead to request failures.
- Insufficient permissions or invalid API key will result in authentication errors.
- Specifying non-existent vectors or points will not delete anything but may not always throw errors.
Error messages:
- Authentication errors: Check API key validity and credential setup.
- Validation errors: Ensure required fields like collection name and vectors/points are correctly provided.
- Network errors: Verify connectivity to the Qdrant server and correct base URL configuration.