Actions26
- Delete Collection
- Get Collection
- Check Collection Exists
- Create Collection
- Update Collection
- Retrieve Point
- Retrieve Points
- Upsert Points
- Delete Points
- Update Vectors
- Delete Vectors
- Set Payload
- Overwrite Payload
- Delete Payload
- Clear Payload
- Batch Update Points
- Scroll Points
- Count Points
- Query Points
- Query Batch Points
- Query Points Groups
- Matrix Pairs
- Matrix Offsets
- Payload Facets
- Create Payload Index
- Delete Payload Index
Overview
This node integrates with Qdrant, a vector search engine and database, allowing users to manage collections and their payload indexes. Specifically, the "Create Payload Index" operation enables creating an index on a specified field within a collection. This improves query performance when filtering or searching based on that field's values.
Common scenarios include:
- Enhancing search speed by indexing frequently queried fields.
- Structuring data in Qdrant collections for optimized retrieval.
- Preparing collections for complex queries involving payload filters.
For example, if you have a collection of documents with metadata fields like "author" or "category," creating a payload index on these fields will accelerate searches filtered by those attributes.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The name of the collection in Qdrant where the payload index will be created. |
| Field Name | The specific field within the collection's 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 to wait for the index creation operation to complete. |
| Ordering | Defines the consistency guarantees for the operation; options are Weak, Medium, Strong. |
Output
The node outputs JSON data representing the result of the payload index creation request. This typically includes confirmation of success or details about the created index. There is no binary output associated with this operation.
Dependencies
- Requires connection to a Qdrant instance via an API URL and an API key credential configured in n8n.
- The node depends on the Qdrant REST API to perform operations.
- Proper network access and authentication credentials must be set up in n8n for successful communication.
Troubleshooting
Common Issues:
- Incorrect collection or field names may cause errors or failed index creation.
- Invalid JSON schema for the field can lead to request rejection.
- Network or authentication failures if API credentials or URLs are misconfigured.
Error Messages:
- "Collection not found" — Verify the collection name exists in Qdrant.
- "Invalid field schema" — Check the JSON schema syntax and correctness.
- "Authentication failed" — Confirm API key and URL settings in n8n credentials.
- Timeouts or network errors — Ensure connectivity to the Qdrant server.
Resolving these usually involves verifying input parameters, checking credentials, and ensuring the Qdrant service is reachable.
Links and References
- Qdrant Official Website
- Qdrant API Documentation
- n8n Documentation (for general usage guidance)