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 and database. Specifically, the "Delete Collection" operation allows users to delete an entire collection from their Qdrant instance. This is useful when you want to remove all data and metadata associated with a particular collection, for example, when cleaning up unused collections or resetting your dataset.
Practical examples:
- Removing outdated or test collections to free up storage.
- Automating cleanup of collections after batch processing.
- Managing lifecycle of collections in a dynamic environment where collections are created and deleted frequently.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The name of the collection to delete |
Output
The output JSON will typically contain the response from the Qdrant API confirming the deletion status of the specified collection. It may include success confirmation or error details if the deletion failed.
This node does not output binary data.
Dependencies
- Requires connection to a Qdrant instance via an API URL.
- Needs an API key credential configured in n8n for authentication with the Qdrant service.
- The base URL and authentication token must be set in the node credentials.
Troubleshooting
- Collection Not Found: If the specified collection name does not exist, the node may return an error indicating the collection was not found. Verify the collection name spelling and existence.
- Authentication Errors: If the API key or URL is incorrect or missing, authentication will fail. Ensure credentials are correctly configured.
- Network Issues: Connectivity problems to the Qdrant server can cause timeouts or failures. Check network access and server availability.
- Permission Denied: Insufficient permissions on the API key may prevent deletion. Confirm that the API key has rights to delete collections.