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 designed for managing and searching large collections of vectors. Specifically, the "Get Collection" operation retrieves metadata or details about a named collection stored in Qdrant.
This node is beneficial when you want to programmatically access information about existing collections in your Qdrant instance, such as verifying their existence, inspecting configuration, or preparing for further operations like querying or updating points within that collection.
Practical examples include:
- Fetching collection details before performing vector searches.
- Validating collection configurations during automated workflows.
- Integrating Qdrant collection metadata retrieval into data pipelines.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The name of the collection in Qdrant whose details you want to retrieve. This is a required string input. |
Output
The node outputs JSON data containing the details of the requested collection from Qdrant. This typically includes metadata such as collection configuration, status, vector size, distance metric, and other relevant properties describing the collection.
No binary data output is produced by this operation.
Dependencies
- Requires connection to a Qdrant instance via an API endpoint URL.
- Needs an API key credential (or equivalent authentication token) configured in n8n to authorize requests to the Qdrant service.
- The base URL and authentication credentials must be set up properly in the node's credential configuration.
Troubleshooting
- Common issues:
- Incorrect or missing collection name will cause the request to fail or return an error indicating the collection does not exist.
- Misconfigured API URL or invalid authentication credentials will result in connection errors or authorization failures.
- Error messages:
- "Collection not found" indicates the specified collection name does not exist in Qdrant.
- "Unauthorized" or "Authentication failed" suggests problems with the API key or credentials.
- Resolutions:
- Verify the collection name spelling and existence in your Qdrant instance.
- Check and update the API URL and credentials in n8n settings.
- Ensure network connectivity to the Qdrant server.