Actions11
Overview
This node provides advanced integration with the Qdrant vector search engine, allowing users to perform a wide range of operations on Qdrant collections and points. It supports managing collections (creating, updating, deleting, listing), manipulating points within collections (upserting, updating, retrieving, deleting), searching points by vector similarity, and counting points with optional filters.
Typical use cases include:
- Managing vector collections for machine learning or AI applications.
- Performing similarity searches on embedding vectors to find related items.
- Maintaining and updating large datasets of vectorized data points.
- Integrating Qdrant's vector search capabilities into automated workflows.
For example, you could use this node to update the configuration of an existing collection, or to upsert new points representing document embeddings for semantic search.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The name of the Qdrant collection to operate on. Supports expressions for dynamic values. |
| Collection Config (JSON) | Raw JSON configuration for the collection, including vector size, replication factor, etc. Used when creating or updating a collection. Supports expressions. |
Output
The node outputs a JSON object containing the response from the Qdrant API corresponding to the selected operation. The structure varies depending on the operation:
- For collection operations (create, update, get info, list, delete), it returns details about the collection or success status.
- For point operations (get, upsert, update, delete), it returns information about the affected points.
- For search operations, it returns an array of matching points with their metadata and similarity scores.
- For count operations, it returns the number of points matching the filter criteria.
No binary data output is produced by this node.
Dependencies
- Requires an active Qdrant API endpoint URL and an API key credential configured in n8n.
- Uses the official Qdrant JavaScript client library (
@qdrant/js-client-rest) bundled within the node.
Troubleshooting
- Missing Collection Name: Operations require a collection name; ensure this property is set and not empty.
- Invalid Collection Config JSON: When creating or updating collections, the config must be valid JSON; malformed input will cause errors.
- Missing Required Parameters: Certain operations require specific inputs (e.g., point IDs for retrieval/deletion, points array for upsert/update, search vector and limit for search). Omitting these will trigger errors.
- API Errors: Network issues, invalid credentials, or incorrect API usage may result in API errors surfaced by the node.
- To resolve errors, verify all required parameters are provided, JSON inputs are well-formed, and credentials are correctly configured.