Actions26
- Collection Actions
- Payload Actions
- Point Actions
- Search Actions
- Vector Actions
Overview
The node provides an interface to Qdrant, a vector search engine, focusing here on the "Payload" resource with the "Set Payload" operation. This operation allows users to set or update payload data (metadata) for specific points within a named collection in Qdrant.
Typical use cases include enriching vector points with additional metadata after they have been inserted, such as tags, categories, or custom attributes that can be used later for filtering or searching. For example, you might add user demographic information to points representing user embeddings or product details to points representing product vectors.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The target collection where points reside. Can be selected from a searchable list of existing collections or specified by name directly. |
| Payload | JSON object containing the key-value pairs to set as payload for the selected points. |
| Point IDs | JSON array specifying explicit point IDs to update. If provided, only these points will be affected. |
| Filter | JSON object defining conditions to select points based on their current payload or other criteria. Only points matching this filter will be updated. |
| Key | A string path indicating where in each point's payload the new payload should be assigned. For example, setting a nested property rather than replacing the entire payload. |
| Shard Key | JSON value(s) specifying which shards to search for points. If omitted, all shards are searched. Useful for optimizing queries in sharded collections. |
| Wait | Boolean flag indicating whether the operation should wait until changes are fully applied before returning. |
| Ordering | Defines the consistency guarantee level for the operation. Options are: Weak, Medium, Strong — affecting how strictly the operation is ordered relative to others. |
Output
The node outputs JSON data representing the result of the payload update operation. This typically includes status information about the update request, such as success confirmation or error details.
No binary data output is involved in this operation.
Dependencies
- Requires connection to a Qdrant instance via its REST API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL of the Qdrant service must be set in the node credentials.
Troubleshooting
Common issues:
- Incorrect collection name or non-existent collection will cause errors.
- Malformed JSON in the Payload, Point IDs, Filter, or Shard Key fields can lead to request failures.
- Specifying point IDs or filters that do not match any points results in no updates.
- Insufficient permissions or invalid API keys cause authorization errors.
Error messages and resolutions:
- "Collection not found": Verify the collection name is correct and exists.
- "Invalid JSON format": Check the syntax of JSON inputs for Payload, Points, Filter, and Shard Key.
- "Unauthorized" or "Authentication failed": Confirm API credentials are valid and properly configured.
- "No points matched": Adjust the filter or point IDs to ensure they correspond to existing points.