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 "Scroll Points" operation allows users to paginate through points stored in a named collection. This is useful for retrieving large datasets incrementally without loading all data at once.
Common scenarios include:
- Exporting or processing large sets of vector points from a Qdrant collection.
- Implementing custom pagination or batch processing workflows on vector data.
- Filtering and sorting points based on payload fields or other criteria.
For example, you might use this node to scroll through all points in a collection named "products", fetching 50 points per page, optionally filtering by some attribute, and including payload data for further analysis.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The name of the Qdrant collection from which to scroll points. |
| Limit | Maximum number of points to return in one page (page size). |
| Filter | JSON object specifying conditions to filter points (only points satisfying these are returned). |
| With Payload | Boolean indicating whether to include the payload data of each point in the response. |
| With Vector | Boolean indicating whether to include the vector data of each point in the response. |
| Offset | ID of the point to start reading from (used for pagination). |
| Order By | JSON object defining how to order the results by a payload field. |
| Shard Key | JSON object specifying which shards to query; if omitted, all shards are searched. |
| Consistency | Read consistency level for the operation; options: Majority, Quorum, All. |
| Timeout | Request timeout in seconds, overriding global timeout if set. |
Output
The output contains a JSON array of points retrieved from the specified collection. Each point includes:
- Its unique identifier.
- Optionally, the payload data if
With Payloadis true. - Optionally, the vector data if
With Vectoris true.
This structure enables downstream nodes to process or analyze the points' metadata and vector embeddings as needed.
If binary data were involved, it would be summarized here, but this operation deals primarily with JSON data representing points.
Dependencies
- Requires connection to a Qdrant service endpoint.
- Needs an API key credential configured in n8n for authentication.
- The base URL and authentication token must be set in the node credentials.
Troubleshooting
- Timeouts: If requests time out, consider increasing the
Timeoutproperty or checking network connectivity. - Invalid Collection Name: Errors may occur if the specified collection does not exist; verify the collection name.
- Filter Syntax: Malformed JSON in the
FilterorOrder Byproperties can cause errors; ensure valid JSON format. - Permission Issues: Authentication failures indicate problems with the API key or access rights.
- Offset Handling: Incorrect offset values may result in empty responses or repeated data; ensure correct usage for pagination.