STEP 1
Select Milvus in workflow
Pick Milvus app in the workflow builder [4] - just one click to select the app.
Milvus Integration
Open-source vector database for storing and searching embedding data at scale. Use Milvus as a workflow source of truth for querying, inserting, updating, and syncing data. Start from Watch Entities, then connect database actions like Conduct a Query and Get Entities.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Supported triggers and actions for Milvus integration
Triggers can detect changes in Milvus and run actions that can create, search or modify data inside Milvus automatically [3] — exactly how you set them.
- Watch EntitiesTriggers when a new entity is created.
- Watch FieldsTriggers when a new field is created or an existing field is updated.
- Watch Vector FieldsTriggers when a new vector field is created.
- Conduct a QueryConducts a query on scalar fields in a collection.
- Get EntitiesRetrieves entities matching the provided IDs.
- List CollectionsRetrieves a list of collections from the service.
- Search Similarity in a CollectionConducts a similarity search on a vector field in a collection.
- Create a CollectionCreates a new collection in the specified service.
- Delete an EntityDeletes a specified entity from the service.
- Describe a CollectionDescribes a collection by providing details about its content and attributes.
- Drop a CollectionDrops a collection from the database.
- Insert Entities into a CollectionInserts one or more entities into a collection.
- Make an API CallMakes an arbitrary call to the specified API.
- Upsert Entities into a CollectionUpserts one or more entities into a collection.
How to integrate Milvus in automation workflow?
3 simple steps to make your Milvus connected with other apps in automation workflows on WEXTL. Up to 10 minutes integration set up.
STEP 2
Connect Milvus
When prompted, authorize access to Milvus in WEXTL once. Milvus credentials are encrypted and never shared with WEXTL. Authorization will be reused in any future API calls [3].
WEXTL wants to integrate with your Milvus account. Approve?
STEP 3
Build a workflow
Build your workflow with Milvus yourself or with WEXTL® AI Builder. Connect Milvus to any available integrations [5], or use HTTP node to go beyond them.
Milvus
How Milvus connects and integrates with WEXTL
Save and approve your credentials once — WEXTL® stores authorization information encrypted and reuses the authentication whenever Milvus 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 Milvus supports.
The following table illustrates what fields Milvus integration require during authorization flow inside our workflow builder [4].
Video slide demonstrates how Milvus is connected in WEXTL builder [4].
| Field | Type | Help |
|---|---|---|
HostRequired | url | The URI of your instance, including the protocol (e.g., |
PortRequired | integer | The port of your instance. Defaults to |
UsernameRequired | text | The username used to access your instance. Defaults to |
PasswordRequired | password | The password used to access your instance. |
Connect Milvus to popular apps on WEXTL
Enter a name of the other app you want to sync with Milvus below. Click on selected app to explore integration options with Milvus. If the app you search for is not available in WEXTL yet, you can use HTTP node [10] instead to integrate it directly.
Example automation with Milvus integration
Select Watch Entities trigger from Milvus - this will be a starting point in your automation. Whenever event happens in Milvus, workflow will start [7] from Watch Entities node.
Search for Insert Entities into a Collection, connect it as the next step of integration sequence. You can use filters between Watch Entities and Insert Entities into a Collection, so only important data pass from Watch Entities to the next step. WEXTL gives you full control over the process of Milvus automation. All parts of workflow are visible on the canvas [4].
Milvus on WEXTL has 14 modules for crafting database automations. Explore Milvus documentation for more.
Video slide demonstrates how Watch Entities and Insert Entities into a Collection [6] nodes are used in Milvus workflow.
Frequently asked questions
Common questions about automating Milvus in your workflows.
Milvus has 3 triggers, including "Watch Entities", "Watch Fields", and "Watch Vector Fields". Triggers are start points of the workflow, and automations may start from them.
Integration has 11 actions, including "Conduct a Query", "Get Entities", and "List Collections", and more. Refer to our Milvus Documentation for detailed inputs and outputs.
No. Most automations are built visually on the canvas by picking triggers, actions, and mapping fields. You can add custom JavaScript with Functions when advanced logic is needed — but our customers do that in rare cases [4].
Yes. Connections are authenticated per account, credentials are encrypted at rest, and you can enforce approvals and team-level access controls on any automation.
The Milvus integration on WEXTL runs directly on its vendor public API — every field name, authentication method, and rate limit is controlled by Milvus official API and covered in documentation [3]. WEXTL handles the request signing and pagination for you.
Absolutely. Where Milvus provides native webhooks, you can use instant triggers to eliminate polling delay. For custom webhooks, WEXTL offers Custom Webhook node, so you can start automation whenever Milvus or any other service sends event to webhook URL.
WEXTL is an AI-first visual canvas. The platform allows you to describe automation in plain text — and AI will wire nodes for Milvus inside the workflow builder [4]. You can also use built-in workflow nodes (AI Agent, Human in the Loop, Condition, Aggregate Results) in pair with Milvus modules to craft complex integration flows with branches, filtering, and conditional logic. There are absolutely no limits of what you can build.
References
List of sources used to gather information about the Milvus integration.
- Milvus integration source code, module specs and credentials implementation.
- Internal Milvus integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official Milvus vendor API documentation — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
- WEXTL® Apps Library
- WEXTL® Milvus App Documentation
- WEXTL® Workflow Scheduler
- WEXTL® HTTP node documentation