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 Qdrant, a vector search engine and database. Specifically, the "Query Batch Points" operation allows users to perform multiple search queries in a single batch request against a specified collection. This is useful for scenarios where you want to efficiently retrieve or compare multiple sets of points (vectors) from the collection simultaneously, such as running several similarity searches or ID lookups in one go.
Practical examples include:
- Performing multiple vector similarity searches with different query vectors at once.
- Combining ID-based retrievals and complex queries in a single batch to reduce API calls.
- Running batch analytics or filtering operations on stored vector data.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The name of the collection in Qdrant where the batch queries will be executed. |
| Searches | A JSON array representing a list of search requests to perform in batch. Each request can be a vector search, ID search, or a complex query. |
| Consistency | Defines the read consistency guarantees for the operation. Options: Majority, Quorum, All. |
| Timeout | Optional override for the global timeout setting for this request, specified in seconds. Default is 100. |
Output
The output contains a json field that holds the results of the batch query operation. This typically includes an array of responses corresponding to each individual search request submitted in the batch. Each response contains the matched points and their metadata according to the query parameters.
If the node supports binary data output (not explicitly shown here), it would represent any associated binary payloads returned by Qdrant, but this operation primarily deals with JSON structured search results.
Dependencies
- Requires connection to a Qdrant instance via an API endpoint URL.
- Needs an API key or token credential configured in n8n to authenticate requests to Qdrant.
- The node uses HTTP requests with JSON payloads to communicate with the Qdrant service.
Troubleshooting
Common issues:
- Invalid or missing collection name will cause the request to fail.
- Malformed JSON in the "Searches" property can lead to parsing errors.
- Network or authentication failures if the API credentials or URL are incorrect.
- Timeout errors if the request takes longer than the specified timeout value.
Error messages:
- "Collection not found": Verify the collection name exists in your Qdrant instance.
- "Invalid search request format": Check the structure of each search object in the batch.
- "Authentication failed": Confirm that the API key/token is valid and has necessary permissions.
- "Request timed out": Increase the timeout value or check network connectivity.