Actions11
Overview
This node provides advanced integration with the Qdrant vector search engine, allowing users to perform a wide range of operations on Qdrant collections and points. It supports managing collections (create, update, delete, get info, list), manipulating points within collections (upsert, update, delete, retrieve by IDs), searching points by vector similarity, and counting points with optional filters.
The "Delete Collection" operation specifically deletes an entire collection from Qdrant by its name. This is useful when you want to remove all data and metadata associated with a collection permanently.
Common scenarios:
- Cleaning up unused or obsolete collections in your Qdrant instance.
- Automating lifecycle management of collections as part of a data pipeline.
- Resetting a collection before re-importing new data.
Example:
You have a collection named "products" storing product embeddings for search. When the product catalog is deprecated, you can use this node's Delete Collection operation to remove the "products" collection entirely.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The name of the Qdrant collection to operate on. Supports expressions to dynamically set it. |
Output
The output JSON contains a single field indicating success:
{
"success": true
}
This confirms that the collection was deleted successfully.
No binary data output is produced by this operation.
Dependencies
- Requires a Qdrant API endpoint URL and an API key credential configured in n8n.
- Uses the official Qdrant JavaScript client library (
@qdrant/js-client-rest) to communicate with the Qdrant service.
Troubleshooting
- Missing Collection Name: If the "Collection Name" property is empty, the node will throw an error stating that the collection name is required.
- Collection Not Found: If the specified collection does not exist, the Qdrant API may return an error which will be surfaced by the node.
- API Authentication Errors: Ensure the API key and URL credentials are correctly configured; otherwise, authentication errors will occur.
- Network Issues: Connectivity problems to the Qdrant server will cause request failures.
- Permission Issues: The API key must have sufficient permissions to delete collections.
To resolve errors:
- Verify the collection name is correct and exists.
- Check API credentials and network connectivity.
- Review Qdrant server logs for more details if available.