> ## Documentation Index
> Fetch the complete documentation index at: https://docs.engini.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Qdrant

Let's learn how to connect Engini to Qdrant.

Use Qdrant in your workflows to store, update, delete and look up points in your vector collections, search for similar points, and manage your collections.

To get started, create an account at [Qdrant Cloud](https://cloud.qdrant.io).

## Add a Connection to Qdrant in Engini

### Prerequisites

* A Qdrant Cloud account.
* A Qdrant cluster. A free cluster is enough to get started.
* The Cluster URL of your cluster and a Database API key for it.

### Retrieve your Qdrant Cluster URL and API Key

1. Sign in to [Qdrant Cloud](https://cloud.qdrant.io).
2. Open *Clusters* and click *Create*. Choose the *Free* plan, enter a name for the cluster and create it. The name can contain only letters, numbers, `-` and `_`.
3. When the cluster is ready, open it and copy its *Endpoint*. This is your Cluster URL, for example `https://xyz.eu-central-1-0.aws.cloud.qdrant.io:6333`.
4. In the cluster, open *API Keys* and click *Create*. Give the key a name and create it.
5. Copy the key right away. Qdrant shows it only once.

### Connecting Engini to Qdrant

1. Enter your Engini account at [https://app.engini.io](https://app.engini.io/).

2. Navigate to the Connections page by clicking on Connections in the left sidebar or by clicking [here](https://app.engini.io/connections).

   ![Engini - Connections page](https://mintcdn.com/engini/9SL8Lj_vCdXYHVsm/help/assets/apps/qdrant/connections-page.png?fit=max\&auto=format\&n=9SL8Lj_vCdXYHVsm\&q=85\&s=723ed2984b3477953235dc6988722ad5)

3. Click on the "New Integration" option located at the top bar.

   ![Engini - New Integration button](https://mintcdn.com/engini/9SL8Lj_vCdXYHVsm/help/assets/apps/qdrant/new-integration-button.png?fit=max\&auto=format\&n=9SL8Lj_vCdXYHVsm\&q=85\&s=5f5d0a281079f9d5fd0c6787411a1ac2)

4. Choose the Qdrant option from the available applications.

   ![Qdrant - Choose Application](https://mintcdn.com/engini/9SL8Lj_vCdXYHVsm/help/assets/apps/qdrant/qdrant-choose-application.png?fit=max\&auto=format\&n=9SL8Lj_vCdXYHVsm\&q=85\&s=90f1d308139791b26917ebf92ad62cd9)

5. Enter the following details in the "New Integration" form and press Save:

   ![Qdrant - New Integration form](https://mintcdn.com/engini/9SL8Lj_vCdXYHVsm/help/assets/apps/qdrant/qdrant-new-integration.png?fit=max\&auto=format\&n=9SL8Lj_vCdXYHVsm\&q=85\&s=0a7f3acb661c8c378a86353316269a69)

   <ol>
     <li>*Connection Name -* Enter a name that helps identify the Qdrant connection.</li>
     <li>*Cluster URL -* Enter the Endpoint of your Qdrant cluster, including the port, for example `https://xyz.eu-central-1-0.aws.cloud.qdrant.io:6333`. You can copy it from the cluster page in Qdrant Cloud.</li>
     <li>*API Key -* Enter the Database API key you created for the cluster in Qdrant Cloud.</li>
     <li>*Save -* Click Save to create the connection.</li>
   </ol>

## Actions

Every action that works with a collection or its points starts with a *Collection Id* field. Click it and choose one of the collections in your Qdrant cluster from the list, or map the collection name from the output of the [Get Collections](#get-collections) action. Point ids are the ids you chose when you created the points. You can also map them from the output of [Get Points](#get-points) or [Get Similar Points](#get-similar-points).

**Note:** On Qdrant Cloud, filtering on a payload field requires an index on that field. A filter on a field that has no index is rejected by Qdrant. To filter on a payload field, first create an index for it with the [Create Payload Index](#create-payload-index) action.

### Count Points

Counts the points in a collection, or only the points that match a filter.

![Qdrant - Count Points action](https://mintcdn.com/engini/9SL8Lj_vCdXYHVsm/help/assets/apps/qdrant/qdrant-count-points.png?fit=max\&auto=format\&n=9SL8Lj_vCdXYHVsm\&q=85\&s=f17248297a9aa1ddbd41867a91aa7e03)

1. *Collection Id -* The collection to count the points in. Choose it from the list, or map its name from Get Collections.
2. *Add Filter -* Click Add Filter to define conditions that narrow down the data list and return only the relevant items. To learn more about using filters, [click here](https://docs.engini.ai/help/workflows/workflow-editor.md#add-filters).

The filters you can add are the following, both optional:

* *Filter -* Count only the points that match this filter, written as a Qdrant filter in JSON. In the example, `color` is a payload field of your points and `red` is the value to match: `{"must":[{"key":"color","match":{"value":"red"}}]}`. The payload field needs an index first (see the note above). Leave it out to count every point.
* *Exact -* Choose Yes for an exact count, which can be slower on large collections, or No for a faster approximate count. The default is Yes.

### Create Collection

Creates a new, empty collection in your cluster.

![Qdrant - Create Collection action](https://mintcdn.com/engini/9SL8Lj_vCdXYHVsm/help/assets/apps/qdrant/qdrant-create-collection.png?fit=max\&auto=format\&n=9SL8Lj_vCdXYHVsm\&q=85\&s=3800bd76cee41031b79d46dc59930005)

1. *Collection Id -* The name of the new collection. Type a name that does not exist in your cluster yet, for example `my-collection`. The other actions then list it in their Collection Id field.
2. *Vector Size -* The number of values in each vector, for example `1536`. Enter the output size of the embedding model you use to create your vectors (the model's documentation states it), because every point you add later must have exactly this many values.
3. *Distance -* How Qdrant measures how close two vectors are. Choose Cosine, Dot, Euclid or Manhattan from the list. Cosine is the usual choice for text embeddings, but check which one your embedding model recommends.
4. *Add Field -* Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, [click here](https://docs.engini.ai/help/workflows/workflow-editor.md#add-fields).

All of the following are optional and are added through Add Field:

* *Shard Number -* The number of shards to split the collection into, for example `1`. Leave it out to use the Qdrant default.
* *Replication Factor -* The number of copies kept of each shard, for example `1`. Leave it out to use the Qdrant default.
* *Write Consistency Factor -* The number of copies that must confirm a write, for example `1`. Leave it out to use the Qdrant default.
* *HNSW Config -* Settings of the search index, written as JSON, for example `{"m":16}`. The setting names are listed in the Qdrant documentation under collection configuration. Leave it out to use the defaults.
* *Optimizers Config -* Settings of the background optimizer, written as JSON, for example `{"indexing_threshold":20000}`. The setting names are listed in the Qdrant documentation. Leave it out to use the defaults.
* *Sparse Vectors -* Settings for sparse vectors, written as JSON, where each key is the name of a sparse vector, for example `{"text":{}}`. Leave it out if you only use regular vectors.
* *Quantization Config -* Settings that compress the stored vectors to save memory, written as JSON, for example `{"scalar":{"type":"int8"}}`. Leave it out to store the vectors uncompressed.

### Create or Update Points

Creates a point in a collection, or replaces it if a point with the same id already exists (a Qdrant upsert).

![Qdrant - Create or Update Points action](https://mintcdn.com/engini/9SL8Lj_vCdXYHVsm/help/assets/apps/qdrant/qdrant-create-or-update-points.png?fit=max\&auto=format\&n=9SL8Lj_vCdXYHVsm\&q=85\&s=f920cb0665d005ca3b869be96e7d1ed9)

1. *Collection Id -* The collection to write the points to. Choose it from the list, or map its name from Get Collections.
2. *Points -* The points to add, as a JSON array. Each point has an `id`, its `vector` and, optionally, a `payload`, for example `[{"id": 1, "vector": [0.1, 0.2, 0.3], "payload": {"color": "red"}}]`. The `id` is a whole number or a UUID that you choose, and using an existing id replaces that point. The `vector` is the list of numbers from your embedding model, for example the output of an AI embedding step mapped into the array, and it must have as many values as the Vector Size of the collection (you can see it in Get Collection). The `payload` is any extra data you want to store with the point, as key and value pairs.
3. *Add Field -* Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, [click here](https://docs.engini.ai/help/workflows/workflow-editor.md#add-fields).

The following is optional and is added through Add Field:

* *Wait For Completion -* Choose Yes from the list to wait until Qdrant has fully applied the change, so the next step can find the points right away, or No to continue as soon as Qdrant has accepted it.

### Create Payload Index

Creates an index on a payload field of a collection. On Qdrant Cloud you need this index before you can filter on that field, in Count Points, Get Points, Get Similar Points, Delete Points or Set Payload.

![Qdrant - Create Payload Index action](https://mintcdn.com/engini/9SL8Lj_vCdXYHVsm/help/assets/apps/qdrant/qdrant-create-payload-index.png?fit=max\&auto=format\&n=9SL8Lj_vCdXYHVsm\&q=85\&s=88a8075a5ebad12c6b6f2ac7edfc30b5)

1. *Collection Id -* The collection to create the index in. Choose it from the list, or map its name from Get Collections.
2. *Field Name -* The name of the payload field to index, for example `city`. Enter the key exactly as it appears in the payload of your points, which you can check in the output of Get Points (With Payload set to Yes).
3. *Field Schema -* The type of the values in that field. Choose Boolean, Datetime, Float, Geo, Integer, Keyword (exact match), Text (full text) or UUID from the list. For example, choose Keyword for a field such as `city` that holds names you match exactly.
4. *Add Field -* Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, [click here](https://docs.engini.ai/help/workflows/workflow-editor.md#add-fields).

The following is optional and is added through Add Field:

* *Wait For Completion -* Choose Yes from the list to wait until Qdrant has fully built the index, so you can filter on the field right after, or No to continue as soon as Qdrant has accepted the request.

### Delete Collection

Deletes a collection and all of its points from your cluster. This cannot be undone.

![Qdrant - Delete Collection action](https://mintcdn.com/engini/9SL8Lj_vCdXYHVsm/help/assets/apps/qdrant/qdrant-delete-collection.png?fit=max\&auto=format\&n=9SL8Lj_vCdXYHVsm\&q=85\&s=7b16b61598b5f14c7531d3938d7c779b)

* *Collection Id -* The collection to delete. Choose it from the list, or map its name from Get Collections. Check it carefully, because the collection and all of its points are removed.

### Delete Points

Deletes points from a collection, either by their ids or by a filter.

![Qdrant - Delete Points action](https://mintcdn.com/engini/9SL8Lj_vCdXYHVsm/help/assets/apps/qdrant/qdrant-delete-points.png?fit=max\&auto=format\&n=9SL8Lj_vCdXYHVsm\&q=85\&s=61a46b83fff261ad9b10e83be8876142)

1. *Collection Id -* The collection the points are in. Choose it from the list, or map its name from Get Collections.
2. *Add Field -* Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, [click here](https://docs.engini.ai/help/workflows/workflow-editor.md#add-fields).

All of the following are optional and are added through Add Field. Use either Point Ids or Filter:

* *Point Ids -* The ids of the points to delete, as a JSON array, for example `[1, 2, 3]`. Use the ids you gave the points when you created them, or map them from the output of Get Points or Get Similar Points.
* *Filter -* Delete the points that match this filter instead, written as JSON. In the example, `color` is a payload field of your points and `red` is the value to match: `{"must":[{"key":"color","match":{"value":"red"}}]}`. The payload field needs an index first (see the note above).

### Get Collection

Gets the details of one collection, such as its vector settings and the number of points in it.

![Qdrant - Get Collection action](https://mintcdn.com/engini/9SL8Lj_vCdXYHVsm/help/assets/apps/qdrant/qdrant-get-collection.png?fit=max\&auto=format\&n=9SL8Lj_vCdXYHVsm\&q=85\&s=377725c62eec86a14bd96a6bdda68c01)

* *Collection Id -* The collection to get. Choose it from the list, or map its name from Get Collections.

### Get Collections

Gets all the collections in your Qdrant cluster. This action has no fields to fill in.

![Qdrant - Get Collections action](https://mintcdn.com/engini/9SL8Lj_vCdXYHVsm/help/assets/apps/qdrant/qdrant-get-collections.png?fit=max\&auto=format\&n=9SL8Lj_vCdXYHVsm\&q=85\&s=abb5e45ae51b023bafd9d72e13ef5052)

### Get Point

Gets one point from a collection by its id.

![Qdrant - Get Point action](https://mintcdn.com/engini/9SL8Lj_vCdXYHVsm/help/assets/apps/qdrant/qdrant-get-point.png?fit=max\&auto=format\&n=9SL8Lj_vCdXYHVsm\&q=85\&s=39319c93d305e81dc8bb6b5c00120581)

1. *Collection Id -* The collection the point is in. Choose it from the list, or map its name from Get Collections.
2. *Point Id -* The id of the point to get, for example `1`. Enter the id you gave the point when you created it, or map it from the output of Get Points or Get Similar Points.

### Get Points

Gets points from a collection, page by page, optionally only those that match a filter.

![Qdrant - Get Points action](https://mintcdn.com/engini/9SL8Lj_vCdXYHVsm/help/assets/apps/qdrant/qdrant-get-points.png?fit=max\&auto=format\&n=9SL8Lj_vCdXYHVsm\&q=85\&s=da4a4c3ce638b32115d015d0da5cef90)

1. *Collection Id -* The collection to read the points from. Choose it from the list, or map its name from Get Collections.
2. *Top N -* You can set the maximum number of points Engini will return, for example `10`. The default is 10.
3. *Add Filter -* Click Add Filter to define conditions that narrow down the data list and return only the relevant items. To learn more about using filters, [click here](https://docs.engini.ai/help/workflows/workflow-editor.md#add-filters).

The filters you can add are the following, all optional:

* *Filter -* Return only the points that match this filter, written as JSON. In the example, `color` is a payload field of your points and `red` is the value to match: `{"must":[{"key":"color","match":{"value":"red"}}]}`. The payload field needs an index first (see the note above). Leave it out to return all points.
* *With Payload -* Choose Yes or No from the list to decide whether each returned point includes its payload (its stored key and value pairs). The default is Yes.
* *With Vector -* Choose Yes or No from the list to decide whether each returned point includes its vector. The default is No, because vectors can be long.

### Get Similar Points

Finds the points in a collection whose vectors are most similar to a vector you provide.

![Qdrant - Get Similar Points action](https://mintcdn.com/engini/9SL8Lj_vCdXYHVsm/help/assets/apps/qdrant/qdrant-get-similar-points.png?fit=max\&auto=format\&n=9SL8Lj_vCdXYHVsm\&q=85\&s=4880ed7be28dbdb31f9e501db4543eba)

1. *Collection Id -* The collection to search. Choose it from the list, or map its name from Get Collections.
2. *Query Vector -* The vector to search with, as a JSON list of numbers, for example `[0.2, 0.1, 0.9]`. Map it from the output of the embedding step that turns your search text into a vector, using the same embedding model as the points in the collection. It must have the same number of values as the Vector Size of the collection.
3. *Top N -* You can set the maximum number of similar points Engini will return, for example `10`. The default is 10.
4. *Add Filter -* Click Add Filter to define conditions that narrow down the data list and return only the relevant items. To learn more about using filters, [click here](https://docs.engini.ai/help/workflows/workflow-editor.md#add-filters).

The filters you can add are the following, all optional:

* *Filter -* Search only among the points that match this filter, written as JSON. In the example, `color` is a payload field of your points and `red` is the value to match: `{"must":[{"key":"color","match":{"value":"red"}}]}`. The payload field needs an index first (see the note above).
* *With Payload -* Choose Yes or No from the list to decide whether each returned point includes its payload (its stored key and value pairs). The default is No.

### Set Payload

Adds or changes values in the payload of existing points. The payload keys you do not send stay as they are.

![Qdrant - Set Payload action](https://mintcdn.com/engini/9SL8Lj_vCdXYHVsm/help/assets/apps/qdrant/qdrant-set-payload.png?fit=max\&auto=format\&n=9SL8Lj_vCdXYHVsm\&q=85\&s=5395dc569e8ac863ce6165c6c0b63a71)

1. *Collection Id -* The collection the points are in. Choose it from the list, or map its name from Get Collections.
2. *Payload -* The values to set, written as JSON key and value pairs, for example `{"color": "red"}` sets the payload field `color` to `red`. Keys that already exist on the points are overwritten and new keys are added.
3. *Add Field -* Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, [click here](https://docs.engini.ai/help/workflows/workflow-editor.md#add-fields).

All of the following are optional and are added through Add Field. Use either Point Ids or Filter:

* *Point Ids -* The ids of the points to update, as a JSON array, for example `[1, 2, 3]`. Use the ids you gave the points when you created them, or map them from the output of Get Points or Get Similar Points.
* *Filter -* Update the points that match this filter instead, written as JSON. In the example, `color` is a payload field of your points and `red` is the value to match: `{"must":[{"key":"color","match":{"value":"red"}}]}`. The payload field needs an index first (see the note above).

### Send API Request

This activity allows you to send a custom API request directly to Qdrant's API.

![Qdrant - Send API Request action](https://mintcdn.com/engini/9SL8Lj_vCdXYHVsm/help/assets/apps/qdrant/qdrant-send-api-request.png?fit=max\&auto=format\&n=9SL8Lj_vCdXYHVsm\&q=85\&s=dc0ab394c84c713c78bcae915b1546b8)

1. *Base Url -* The root URL of the Qdrant API. It is filled in from your Qdrant connection and can't be edited here.
2. *Relative url -* You can specify additional path segments or parameters that need to be added to the end of the Base Url. This allows you to customize the specific request you want to perform. For example, `/collections` lists your collections. The paths are in the Qdrant API reference linked below.
3. *Method -* Select the HTTP method (e.g., Get, Post, Put, Delete, Patch). The default is POST.
4. *Body Type -* Defines the format of the data in the body of your request. The default, application/json, means the body contains a JSON-formatted payload.
   * *application/json* – Sends the request body in JSON format. Commonly used by REST APIs.
   * *custom* – Allows you to define a custom body format by manually setting the Content-Type header. Add a `Content-Type` row in *Add Headers* with the media type you need (for example `application/xml`). With any other Body Type, a Content-Type you type in *Add Headers* is not sent; Engini sets it from the Body Type, and the run history shows it under `headersnotsent`.
   * *application/x-www-form-urlencoded* – Sends the body as URL-encoded key-value pairs, commonly used in form submissions.
   * *file* – Sends a file as the request body.
   * *multipart/form-data* – Sends form data that may include both text fields and files.
   * *text/html* – Sends the request body as HTML content.
   * *text/plain* – Sends the request body as plain text.
   * *text/xml* – Sends the request body in XML format.
5. *Body -* Contains any data that is being sent to the server.
6. *Add Headers -* Additional metadata about the request, such as the type of data Engini can accept, the length of the request body, and authentication information.
7. *Add Queries -* The query refers to the parameters or data that are included in the URL of an HTTP request to provide additional information or instructions to the server.

For the full list of endpoints, see the [Qdrant API reference](https://api.qdrant.tech/api-reference).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.