# Qdrant integrations: collections and points

> Create a collection, create a snapshot and update collection aliases in Qdrant. Connect Qdrant to the rest of your data and analytics stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/qdrant-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

Qdrant is a vector database and search engine that stores embeddings with attached data and finds the closest matches for semantic search and AI retrieval. Tray.ai connects to Qdrant through the HTTP Connector, so your workflows can call the Qdrant API alongside the rest of your stack.

## Use cases

### Collections

Read, create, update, and delete collections in Qdrant from any Tray.ai workflow. The Qdrant API covers calls such as list all collections and create a collection.

- List all collections
- Create a collection
- Update collection parameters

### Points

Read, update, and delete points in Qdrant from any Tray.ai workflow. The Qdrant API covers calls such as upsert points and retrieve points.

- Upsert points
- Retrieve points
- Delete points

### Search

Read search in Qdrant from any Tray.ai workflow. The Qdrant API covers calls such as query points and query points in batch.

- Query points
- Query points in batch
- Query point groups

### Snapshots

Read, create, and delete snapshots in Qdrant from any Tray.ai workflow. The Qdrant API covers calls such as list collection snapshots and create a snapshot.

- List collection snapshots
- Create a snapshot
- Download a snapshot

### Aliases

Read and update aliases in Qdrant from any Tray.ai workflow. The Qdrant API covers calls such as list all aliases and update collection aliases.

- List all aliases
- Update collection aliases

## Challenges Tray.ai solves

### Keeping Qdrant credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Qdrant credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Qdrant API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Qdrant API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Qdrant?

Yes. Tray.ai connects to Qdrant through the HTTP Connector, which calls the Qdrant API directly. Any call the Qdrant API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Qdrant?

The Qdrant API uses an API key in a request header and a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Qdrant connector?

Qdrant runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Qdrant connector from the Qdrant API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/
