Actions26
- Collection Actions
- Payload Actions
- Point Actions
- Search Actions
- Vector Actions
Overview
This node integrates with Qdrant, a vector search engine, to manage payload indexes within collections. Specifically, the "Create Payload Index" operation allows users to create an index on a specified field in a collection's payload data. This is useful for optimizing query performance and enabling efficient filtering or searching based on that field.
Common scenarios include:
- Preparing a collection for faster queries by indexing frequently filtered fields.
- Structuring payload data to support complex search operations.
- Managing large datasets where indexing specific fields improves response times.
For example, if you have a collection of documents with metadata fields like "category" or "author," creating a payload index on these fields can speed up searches filtering by those attributes.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The target collection where the payload index will be created. Can be selected from a list of existing collections or entered manually by name. |
| Field Name | The name of the field within the payload to create the index for. |
| Field Schema | JSON schema describing the structure/type of the field to be indexed. |
| Wait | Boolean flag indicating whether the operation should wait until the index creation is fully completed before proceeding. Defaults to true. |
| Ordering | Defines the ordering guarantees for the operation. Options are: Weak, Medium, Strong. |
Output
The node outputs JSON data representing the result of the index creation operation. This typically includes confirmation details such as success status or any metadata returned by the Qdrant API about the created index.
No binary data output is involved in this operation.
Dependencies
- Requires connection to a Qdrant instance via its REST API.
- An API key or authentication token credential must be configured in n8n to authorize requests.
- The base URL of the Qdrant service must be set in the node credentials.
Troubleshooting
Common issues:
- Incorrect collection name leading to "collection not found" errors.
- Invalid JSON schema format causing request validation failures.
- Network or authentication errors if the Qdrant service is unreachable or credentials are invalid.
Error messages and resolutions:
- "Collection does not exist": Verify the collection name is correct and exists in Qdrant.
- "Invalid field schema": Ensure the JSON schema provided is valid and matches expected formats.
- Timeout or network errors: Check connectivity to the Qdrant server and confirm credentials are properly configured.
- Operation failed due to ordering parameter: Use appropriate ordering level supported by your Qdrant setup.