Actions26
- Collection Actions
- Payload Actions
- Point Actions
- Search Actions
- Vector Actions
Overview
The node provides an interface to perform batch update operations on points within a Qdrant collection. This operation allows users to apply multiple modifications in one request, such as upserting points, updating vectors, setting or deleting payload data, and clearing payloads for points in a specified collection.
This is beneficial when you need to efficiently update many points at once without sending individual requests for each point. For example, you might want to update the vector embeddings of multiple points after reprocessing data, or remove certain metadata fields from a batch of points.
Practical examples:
- Bulk updating vector representations of items in a recommendation system.
- Removing outdated tags or attributes from many points simultaneously.
- Upserting new points with associated payloads in a single batch operation.
Properties
| Name | Meaning |
|---|---|
| Collection Name | Specifies the target collection where the batch update will be applied. You can select from an existing list of collections or specify the collection name directly. |
| Operations | A JSON array describing the list of operations to perform on points. Supported operations include: upsert, update_vectors, set_payload, delete_payload, delete_vectors, and clear_payload. |
| Wait | Boolean flag indicating whether the node should wait for the changes to be fully applied before continuing execution. |
| Ordering | Defines the ordering guarantees for the batch update operation. Options are: Weak, Medium, and Strong, which control how strictly the order of operations is enforced during processing. |
Output
The node outputs JSON data representing the result of the batch update operation. This typically includes confirmation of the successful application of the requested operations or any errors encountered per point.
If the node supports binary data output (not indicated here), it would represent related binary content, but this operation primarily deals with JSON responses confirming updates.
Dependencies
- Requires connection to a Qdrant service endpoint, configured via credentials that provide the base URL and authentication (e.g., an API key).
- The node depends on the Qdrant REST API to perform batch update operations on points.
- Proper configuration of the API credentials in n8n is necessary for successful communication.
Troubleshooting
Common issues:
- Invalid collection name or non-existent collection: Ensure the collection specified exists in Qdrant.
- Malformed operations JSON: The
operationsproperty must be a valid JSON array with correctly structured operation objects. - Permission or authentication errors: Verify that the API credentials have sufficient rights to modify the collection.
- Network connectivity problems: Confirm that the Qdrant service URL is reachable from the n8n environment.
Error messages:
- Errors related to invalid operations or unsupported fields usually indicate incorrect formatting in the
operationsJSON. - Authentication failures suggest checking the API key or token validity.
- Timeout or waiting-related errors may require adjusting the
Waitproperty or reviewing network latency.
- Errors related to invalid operations or unsupported fields usually indicate incorrect formatting in the