Actions26
- Collection Actions
- Payload Actions
- Point Actions
- Search Actions
- Vector Actions
Overview
This node operation allows users to delete specific payload keys from points stored in a Qdrant collection. It is useful when you want to selectively remove metadata or attributes (payload) associated with points without deleting the points themselves. For example, if your vector database stores user profiles with various tags as payload, and you want to remove outdated or sensitive tags from certain points, this operation enables that.
Typical use cases include:
- Cleaning up or updating metadata fields on vectors.
- Removing deprecated or incorrect payload keys from selected points.
- Managing payload data dynamically based on filtering criteria.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The target collection from which payload keys will be deleted. You can select an existing collection from a list or specify its name directly. |
| Keys | A JSON array listing the payload keys to remove from the selected points. For example: ["key1", "key2"]. |
| Point IDs | (Optional) A JSON array of point IDs specifying exactly which points to modify. If omitted, other filters apply. |
| Filter | (Optional) A JSON object defining conditions to filter points. Only points matching these conditions will have their payload keys deleted. |
| Shard Key | (Optional) A JSON value specifying shards to restrict the operation to. If not set, all shards are considered. |
| Wait | Boolean flag indicating whether to wait for the deletion changes to be applied before returning. Defaults to true. |
| Ordering | Defines the consistency guarantees for the operation. Options are: Weak, Medium, Strong. This affects how strictly the operation waits for changes to propagate across the system. Default is Weak. |
Output
The node outputs JSON data representing the result of the delete payload operation. Typically, this includes confirmation of success or details about the affected points. The exact structure depends on the underlying API response but generally confirms that the specified payload keys were removed from the targeted points.
No binary data output is produced by this operation.
Dependencies
- Requires connection to a Qdrant vector database instance.
- Needs an API key credential configured in n8n to authenticate requests to the Qdrant REST API.
- The base URL of the Qdrant service must be provided in the credentials configuration.
Troubleshooting
Common issues:
- Specifying non-existent collection names will cause errors; ensure the collection exists.
- Providing invalid JSON for keys, points, filter, or shardKey properties may lead to parsing errors.
- Attempting to delete payload keys from points that do not exist or do not match the filter will result in no changes.
- Network or authentication failures due to incorrect API credentials or URL misconfiguration.
Error messages:
- "Collection not found" — Verify the collection name is correct and exists.
- "Invalid JSON format" — Check the syntax of JSON inputs like keys, points, filter, or shardKey.
- "Unauthorized" — Confirm that the API key credential is valid and has proper permissions.
- Timeout or network errors — Ensure the Qdrant service is reachable and responsive.