Qdrant integration

Vector database: store embeddings with their data and find the closest matches, in your own Qdrant

Help Centre › Connectors

Overview

Qdrant lets a cloud flow store embeddings, with data alongside each, in your own Qdrant and find the closest matches. The points stay in your cluster; Automize keeps nothing.

  • Regions: Qdrant Cloud in any region, or a self-hosted Qdrant reachable from the internet over HTTPS.
  • Plans: Cloud flows only. The bot has no Qdrant connector yet.

Setting up the connection

Auth type: API Key.

  1. In the Qdrant Cloud console, open the cluster and copy its URL, with the port (usually 6333).
  2. Create an API key for the cluster. A self-hosted Qdrant with no key set needs none.
  3. In Automize, open Settings → Connectors → Qdrant → Add connection, and paste the URL and the key.

Rate limits

Set by the cluster's size.


Data model

Cluster ─── Collection (one vector size) ─── Point

    {"id": 1, "vector": [0.1, 0.2, …], "payload": {"source": "invoice.pdf"}}

Available operations

5 operations available. Click any row to jump to its detail.

OperationCategoryWhat it does
Create a collectionGeneralMake a collection for vectors of one size.
Delete pointsGeneralDelete points by id, or the ones that match a filter.
List collectionsGeneralList the collections in the cluster.
Find similar pointsGeneralFind the points closest to a vector.
Upsert pointsGeneralAdd points to a collection, or replace the ones with the same id.

Operations

Create a collection

Make a collection for vectors of one size.

ParameterRequiredTypeDescription
Collection collectionYestextThe collection's name.
Vector size sizeYesintegerHow many numbers each vector has; the embedding model decides this, e.g. 1536.
Distance distanceYesselectHow closeness is measured. Cosine suits most text embeddings.

Tips

  • The size must match the embedding model, e.g. 1536 for OpenAI's text-embedding-3-small.

Delete points

Delete points by id, or the ones that match a filter.

ParameterRequiredTypeDescription
Collection collectionYestextThe collection's name.
Point ids pointsNolistThe ids to delete, e.g. [1, 2, 3].
Filter filterNoobjectDelete the points whose payload matches. Use this or Point ids.
Wait until deleted waitNobooleanAnswer only once the points are gone.

Tips

  • Give Point ids or a Filter.

List collections

List the collections in the cluster.

No input parameters.


Find the points closest to a vector.

ParameterRequiredTypeDescription
Collection collectionYestextThe collection's name.
Vector queryYeslistThe embedding to match, e.g. [0.1, 0.2, …].
How many limitNointegerHow many matches to bring back.
Filter filterNoobjectOnly points whose payload matches, e.g. {"must": [{"key": "source", "match": {"value": "invoice.pdf"}}]}.
Include payload with_payloadNobooleanBring back each match's payload.
Vector name usingNotextFor a collection with named vectors: which one to search.

Tips

  • The matches are in result.points, closest first, each with its score.

Upsert points

Add points to a collection, or replace the ones with the same id.

ParameterRequiredTypeDescription
Collection collectionYestextThe collection's name.
Points pointsYeslistA list of {"id": 1, "vector": [0.1, 0.2, …], "payload": {"source": "invoice.pdf"}}. An id is a whole number or a UUID.
Wait until stored waitNobooleanAnswer only once the points are stored.

FAQ

Where do the vectors come from?
From an embedding step, such as OpenAI's, earlier in the flow.

Related connectors

See it working on your own data

Everything documented here ships with the platform – try the document tools free, or go live in 7 days.