Resources · Make integration

Qdrant Make integrationAutomate Qdrant with Make.

Can Make keep your Qdrant collections fed and searchable without a line of code? The Qdrant Make integration gives you 5 modules: 3 actions and 2 searches. This guide is for builders who already run Qdrant and want to wire it into other apps, from the first connection to a live scenario.

Try the Qdrant integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Qdrant Make integration let you automate?

The Qdrant Make integration links your Qdrant vector database to Make, a visual tool where you build a scenario (the automation itself) by chaining modules, one brick per step. With it, other apps can write points into a collection, read them back, find the closest vectors and remove what is outdated, all without writing code.

Keep a collection in sync with a source app. Each time a record shows up in your CRM or your help desk, Upload a Point sends it to Qdrant, so your semantic search always sees the latest data. Pages such as the Airtable Make integration show what that source side can look like.

Answer with the closest matches. When a question comes in, Search Points asks the collection for the most similar vectors and hands the results to the next module, which can post them, store them or pass them to an AI step.

Clean up on request. When an item is archived at the source, Delete Points removes it from the collection, and Get Points lets you check what is stored before you act.

What Make does not do here: Qdrant has no trigger module, so a scenario starts from another app or from a schedule. When an endpoint is missing from the list, Make an API Call covers it with the same connection. Qdrant also has an n8n node, described in the Qdrant n8n integration page, and the n8n vs Make comparison helps you pick a tool.

Connect

How do you connect your Qdrant account to Make?

  1. 01

    Add a Qdrant module

    In your scenario, click the +, search for Qdrant and pick any of its modules. Then click Create a connection. A connection is your Qdrant account linked to Make once and reused by every Qdrant module you add later.

  2. 02

    Name the connection

    Giving the connection a name is optional, yet it pays off as soon as you work with more than one Qdrant setup. A clear label lets you pick the right account in each module without guessing which is which.

  3. 03

    Authorize and save

    Follow what Make asks for: either approve access on the Qdrant page that opens, or paste the key Qdrant gives you. Click Save, and the module can now list what your account lets it read.

First scenario

Build your first scenario with Qdrant

GoalWhen a new record appears in another app, Make uploads it to your Qdrant collection as a point.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the app that holds your source records, since Qdrant itself has no trigger to start the flow.

  2. 02

    Add Upload a Point

    Click the + on the right of the first module, search for Qdrant and choose Upload a Point. Select your connection, or create it now with Create a connection.

  3. 03

    Map the source data

    Fill the module fields and pick the collection from the list Make shows once the connection exists. Map values from the first module, so each record becomes one point.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received; a bundle is one item passed along, here one record. Check that the point landed in Qdrant.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, which is every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What can the Qdrant modules do?

Qdrant gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Qdrant1

Delete Points

Action

In Make“Deletes points from a collection.”

This action removes points from a collection, so stale or withdrawn content stops showing up in your similarity results.

When to use it
place it after a trigger from your source app that fires when a document is archived or a customer asks for their data to be erased.
Watch out
Make shows no undo step for this module, so as a precaution test it with Run once on a sample collection first.
Qdrant2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Here you reach any endpoint of the Qdrant API from your scenario, using the same connection as the other modules, which covers everything the four ready-made modules leave out.

When to use it
pick it only when no listed module does the job, for example an operation on the collection itself.
Watch out
you write the request yourself, so keep the Qdrant API reference open while you set it up.
Qdrant3

Upload a Point

Action

In Make“Uploads a single point to a collection.”

Use it to send one point into a collection, which keeps your vector store aligned with the records created in your other tools.

When to use it
right after the module that brings in the new item, such as a fresh ticket or a newly published article, so each bundle becomes one point.
Watch out
it handles a single point per run, so every record uploaded counts as one operation on your plan.
Qdrant4

Get Points

Search

In Make“Retrieves points from a collection.”

With this search you read points back from a collection and pass what you find to the next modules of the scenario.

When to use it
before an update or a deletion, to check what is actually stored, or to copy stored points into a sheet for review.
Watch out
a search can return zero, one or several bundles, and each following module runs once per bundle.
Qdrant5

Search Points

Search

In Make“Searches a collection for the most similar vectors.”

Similarity search is what this module brings: it looks through a collection and returns the vectors closest to the one you provide.

When to use it
when a question, a support request or a product description arrives and you want the most related items to feed a reply or a recommendation.
Watch out
a search can return zero, one or several bundles, so plan how the next module handles no match or more than one.
Need help

Need help automating Qdrant with Make?

A person reads every message.

FAQ

Qdrant and Make: frequent questions

01Is the Qdrant Make integration free?
Yes. Qdrant is a standard app in Make, so its modules work on the Free plan. That plan lets you keep 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops an execution after 5 minutes and caps data transfer at 512 MB. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. Usage is counted in credits, where each module run on a bundle is one operation.
02What do you need to connect Qdrant to Make?
A Qdrant account and a Make account are enough to start. The documentation lists no special prerequisite for this app. You add any Qdrant module, click Create a connection, give it a name if you like, then either approve access on the Qdrant page or paste the key Qdrant provides, and save. The same connection is then reused by every Qdrant module of every scenario, so you only do this once per account.
03Does the Qdrant Make integration react in real time?
It depends on what starts your scenario, because Qdrant has no trigger module of its own. The flow begins with another app: an instant trigger from that app fires as soon as something happens, through a webhook, while a scheduled trigger is checked on the scenario schedule, every 15 minutes by default. You can also start the scenario on a plain schedule from the clock on the first module and let the Qdrant modules do their work from there.
04What if a Qdrant module you need is missing in Make?
Use Make an API Call. It lets the scenario call any endpoint of the Qdrant API with the connection you already set up, so you are not limited to uploading, reading, searching and deleting points. You write the request yourself, which asks for a bit more care than a ready-made module. The documentation gives no figure on limits for this app, so test each new call with Run once before switching the scenario on.
05Should you use Make or n8n for Qdrant?
It depends on the tool your team already uses. Qdrant is available in both: Make offers 5 modules, including Make an API Call for anything not covered, and n8n has its own Qdrant node. Neither is ranked above the other here. Look at which modules match your flow, which tool the rest of your automations run on, and how you want to maintain scenarios over time, then test the one that fits.
Same platform

Other docs you might need on this stack.

Browse all integrations