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 "Retrieve Point" operation allows users to fetch a single point (data entry) from a specified collection by its unique ID. This is useful when you want to retrieve detailed information about a specific vector or data point stored in Qdrant.
Common scenarios include:
- Fetching metadata or vector details for a known point ID.
- Verifying the existence or content of a particular point within a collection.
- Integrating Qdrant data retrieval into automated workflows for further processing or analysis.
Example: You have a collection of image embeddings indexed in Qdrant and want to retrieve the embedding vector and associated payload for a specific image by its point ID.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The name of the collection in Qdrant from which to retrieve the point. |
| Point ID | The unique identifier of the point to retrieve from the collection. |
Output
The output contains a JSON object representing the retrieved point. This typically includes:
- The point's unique ID.
- The vector data associated with the point.
- Any payload (metadata) attached to the point.
If the point exists, the JSON will contain these details; if not, the output may be empty or indicate that the point was not found.
The node does not output binary data for this operation.
Dependencies
- Requires connection to a Qdrant instance via an API URL and an API key credential configured in n8n.
- The node uses HTTP requests to communicate with the Qdrant REST API.
- Proper credentials must be set up in n8n to authenticate requests.
Troubleshooting
- Point Not Found: If the specified point ID does not exist in the collection, the node may return an empty result or an error. Verify the point ID and collection name are correct.
- Authentication Errors: Ensure the API key credential and base URL are correctly configured in n8n.
- Network Issues: Connectivity problems to the Qdrant server can cause request failures.
- Invalid Collection Name: Using a non-existent collection name will result in errors; confirm the collection exists before retrieving points.