Actions26
- Collection Actions
- Payload Actions
- Point Actions
- Search Actions
- Vector Actions
Overview
This node integrates with Qdrant, a vector search engine and database, to retrieve a specific point from a collection. The "Retrieve Point" operation fetches detailed information about a single point identified by its unique ID within a specified collection.
Common scenarios for this node include:
- Fetching metadata or payload associated with a particular vector point.
- Retrieving a point's data for further processing or analysis in workflows.
- Validating the existence or content of a point before performing updates or deletions.
Practical example:
- In a recommendation system, after identifying a relevant vector point ID, use this node to get the full details of that point (e.g., user profile or product info) to personalize content.
Properties
| Name | Meaning |
|---|---|
| Collection Name | Specifies the collection from which to retrieve the point. Can be selected from a list of existing collections or entered manually by name. |
| Point ID | The unique identifier of the point to retrieve within the specified collection. |
Output
The node outputs JSON data representing the retrieved point. This typically includes:
- The point's unique ID.
- Its vector data.
- Associated payload (metadata).
- Any additional attributes stored with the point.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Qdrant REST API.
- Needs the base URL of the Qdrant instance configured in the credentials.
- The node sends HTTP requests to the Qdrant API endpoint to perform operations.
Troubleshooting
- Point Not Found: If the specified point ID does not exist in the collection, the node may return an error or empty result. Verify the point ID and collection name are correct.
- Invalid Collection Name: Using a non-existent collection name will cause errors. Use the list mode to select valid collections or ensure the manual name matches exactly.
- Authentication Errors: Ensure the API key and base URL credentials are correctly set up and have sufficient permissions.
- Network Issues: Connectivity problems to the Qdrant server will cause request failures; check network access and server status.