Skip to main content

Qdrant

Bundles contain custom components that support specific third-party integrations with Langflow.

This page describes the components that are available in the Qdrant bundle.

Qdrant vector store

The Qdrant component reads and writes to Qdrant vector stores using an instance of QdrantVectorStore.

About vector store instances

Because Langflow is based on LangChain, vector store components use an instance of LangChain vector store to drive the underlying read and write functions. These instances are provider-specific and configured according to the component's parameters, such as the connection string, index name, and schema.

In component code, this is often instantiated as vector_store, but some vector store components use a different name, such as the provider name.

Some LangChain classes don't expose all possible options as component parameters. Depending on the provider, these options might use default values or allow modification through environment variables, if they are supported in Langflow. For information about specific options, see the LangChain API reference and vector store provider's documentation.

If you use a vector store component to query your vector database, it produces search results that you can pass to downstream components in your flow as a list of Data objects or a tabular DataFrame. If both types are supported, you can set the format near the vector store component's output port in the visual editor.

tip

For a tutorial using a vector database in a flow, see Create a vector RAG chatbot.

Qdrant vector store parameters

You can inspect a vector store component's parameters to learn more about the inputs it accepts, the features it supports, and how to configure it.

Some parameters are hidden by default in the visual editor. You can modify all parameters through the Controls in the component's header menu.

Some parameters are conditional, and they are only available after you set other parameters or select specific options for other parameters. Conditional parameters may not be visible on the Controls pane until you set the required dependencies.

For information about accepted values and functionality, see the Qdrant documentation or inspect component code.

NameTypeDescription
collection_nameStringInput parameter. The name of the Qdrant collection.
hostStringInput parameter. The Qdrant server host.
portIntegerInput parameter. The Qdrant server port.
grpc_portIntegerInput parameter. The Qdrant gRPC port.
api_keySecretStringInput parameter. The API key for Qdrant.
prefixStringInput parameter. The prefix for Qdrant.
timeoutIntegerInput parameter. The timeout for Qdrant operations.
pathStringInput parameter. The path for Qdrant.
urlStringInput parameter. The URL for Qdrant.
distance_funcStringInput parameter. The distance function for vector similarity.
content_payload_keyStringInput parameter. The content payload key.
metadata_payload_keyStringInput parameter. The metadata payload key.
search_queryStringInput parameter. The query for similarity search.
ingest_dataDataInput parameter. The data to be ingested into the vector store.
embeddingEmbeddingsInput parameter. The embedding function to use.
number_of_resultsIntegerInput parameter. The number of results to return in search.
Search