Qdrant icon

Qdrant

Official n8n node to interface with Qdrant - https://qdrant.tech

Actions27

Payload → Clear Payload

AI-generated

Overview

The Clear Payload operation in the Qdrant node is designed to remove or clear specific payload data from points within a specified collection in Qdrant. This operation is useful when you want to selectively clear metadata or attributes associated with points, either by specifying point IDs, applying filters, or targeting specific shards. It supports waiting for the operation to complete and allows control over the ordering guarantees of the operation.

Use Case Examples

  1. Clearing payload data from specific points in a collection by providing their IDs.
  2. Removing payload attributes from points that match certain filter conditions.
  3. Clearing payloads in specific shards of a collection to optimize performance or data management.

Properties

Name Meaning
Collection Name Specifies the name of the collection from which payloads will be cleared. This is a required field and can be selected from a list or entered by name.
Point IDs A JSON array of point IDs to select specific points whose payloads will be cleared.
Filter A JSON object defining conditions to filter points. Only points satisfying these conditions will have their payloads cleared.
Shard Key A JSON object specifying which shards to look for the points. If not specified, the operation will look in all shards.
Wait A boolean flag indicating whether to wait for the changes to actually happen before proceeding.
Ordering Defines the ordering guarantees for the operation, with options for weak, medium, or strong ordering.
Request Options Additional request options such as batching, SSL certificate validation, proxy settings, and timeout configuration to control how the request is sent and handled.

Output

JSON

  • success - Indicates whether the clear payload operation was successful.
  • details - Additional details or metadata about the operation result, such as number of points affected or errors encountered.

Dependencies

  • Requires an API key credential for Qdrant REST API access.

Troubleshooting

  • Ensure the collection name is correct and exists in Qdrant to avoid errors related to missing collections.
  • Validate the JSON format of Point IDs, Filter, and Shard Key inputs to prevent request failures.
  • If the operation times out, consider increasing the timeout setting or checking network connectivity.
  • If SSL certificate validation fails and you trust the endpoint, enable the option to ignore SSL issues.
  • Proxy settings must be correctly configured if used, including authentication details if required.

Links

Discussion