Select Qdrant in workflow
Pick Qdrant app in the workflow builder [4] - just one click to select the app.
Triggers can detect changes in Qdrant and run actions that can create, search or modify data inside Qdrant automatically [3] — exactly how you set them.
3 simple steps to make your Qdrant connected with other apps in automation workflows on WEXTL. Up to 10 minutes integration set up.
Pick Qdrant app in the workflow builder [4] - just one click to select the app.
When prompted, authorize access to Qdrant in WEXTL once. Qdrant credentials are encrypted and never shared with WEXTL. Authorization will be reused in any future API calls [3].
WEXTL wants to integrate with your Qdrant account. Approve?
Build your workflow with Qdrant yourself or with WEXTL® AI Builder. Connect Qdrant to any available integrations [5], or use HTTP node to go beyond them.
Save and approve your credentials once — WEXTL® stores authorization information encrypted and reuses the authentication whenever Qdrant app is called in workflows. That allows your database automations to run without your attention, per defined schedule [7]. Explore documentation [6] for a detailed list of fields that Qdrant supports.
The following table illustrates what fields Qdrant integration require during authorization flow inside our workflow builder [4].
Demonstration of Qdrant connection step inside WEXTL Workflow Builder [4].
| Field | Type | Help |
|---|---|---|
HostingRequired | select | Qdrant Cloud cluster or your own Qdrant instance. |
Cloud Cluster URLRequired | url | https://{cluster-id}.{region}.aws.cloud.qdrant.io — no trailing slash. |
Self-hosted Server URLRequired | url | e.g. http://localhost:6333 — no trailing slash. |
| API Key | password | Sent as the api-key header on every request. Leave empty only if your self-hosted instance has no auth. |
Enter a name of the other app you want to sync with Qdrant below. Click on selected app to explore integration options with Qdrant. If the app you search for is not available in WEXTL yet, you can use HTTP node [10] instead to integrate it directly.
Select Check Collection Exists action from Qdrant - this will be a starting point in your automation. Whenever event happens in Qdrant, workflow will start [7] from Check Collection Exists node.
Search for Create Collection, connect it as the next step of integration sequence. You can use filters between Check Collection Exists and Create Collection, so only important data pass from Check Collection Exists to the next step. WEXTL gives you full control over the process of Qdrant automation. All parts of workflow are visible on the canvas [4].
Qdrant on WEXTL has 70 modules for crafting database automations. Explore Qdrant documentation for more.
Demonstration of how visual Qdrant automation [6] looks in WEXTL.
Common questions about automating Qdrant in your workflows.
List of sources used to gather information about the Qdrant integration.