What actions can I run in Milvus?

11 actions are available, including "Conduct a Query", "Get Entities", and "List Collections", and more. Run them from any trigger in your automation stack — map fields once and they execute automatically.

Do I need to write code to automate this?

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 it is never required.

Is the integration secure?

Yes. Connections are authenticated per account, credentials are encrypted at rest, and you can enforce approvals and team-level access controls on any automation.

Milvus Integrations

Open-source vector database for storing and searching embedding data at scale. Use Milvus as a workflow source of truth — query, insert, and sync without scripts.

Explore Documentation

GDPR
Data Encryption
2FA
Local Data Region

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.

When to use Milvus

Common scenarios where Milvus automation saves time and reduces manual work.

React to "Watch Entities" in Milvus in real time: route the event into CRM, chat, ticketing, or any connected service.
Run "Get Entities" in Milvus from any upstream event — map fields once and let the automation handle the rest.
Include "Watch Vector Fields" from Milvus in larger multi-tool workflows to move data end-to-end without hand-offs.

How to connect

Paste your credentials once — WEXTL® stores them encrypted and reuses the connection across every workflow that needs it.

Full API documentation

Enter your credentials below. WEXTL stores them encrypted and uses them only to call the API on your behalf.

Connecting Milvus to WEXTL®

Field	Type	Help
HostRequired	url	The URI of your instance, including the protocol (e.g., `http://localhost`).
PortRequired	integer	The port of your instance. Defaults to `19530`.
UsernameRequired	text	The username used to access your instance. Defaults to `root`.
PasswordRequired	password	The password used to access your instance.

Use in workflow automation

Start from Milvus’s Watch Entities trigger and the run begins the moment there’s something new — no cron job to babysit, no one remembering to check.

Add Insert Entities into a Collection as the next step, then branch, filter or hand off to the rest of your stack. The whole path stays on one canvas your team can read.

This integration brings 14 ready-made steps for database work, and every run records what went in and what came back.

Milvus workflow on the canvas: Watch Entities then Insert Entities into a Collection

Frequently asked questions

Common questions about automating Milvus in your workflows.

Milvus has 3 triggers, including "Watch Entities", "Watch Fields", and "Watch Vector Fields". Use them to start workflows the moment Milvus events fire — no polling required.

Field

Type

Help

HostRequired

url

The URI of your instance, including the protocol (e.g., http://localhost).

PortRequired

integer

The port of your instance. Defaults to 19530.

UsernameRequired

text

The username used to access your instance. Defaults to root.

PasswordRequired

password

The password used to access your instance.

Use in workflow automation

Start from Milvus’s Watch Entities trigger and the run begins the moment there’s something new — no cron job to babysit, no one remembering to check.

Add Insert Entities into a Collection as the next step, then branch, filter or hand off to the rest of your stack. The whole path stays on one canvas your team can read.

This integration brings 14 ready-made steps for database work, and every run records what went in and what came back.

Milvus Integrations

When to use Milvus

How to connect

Use in workflow automation

Frequently asked questions

Milvus Integrations

When to use Milvus

How to connect

Connect Milvus to any app in workflows

Use in workflow automation

Frequently asked questions

Connect Milvus to any app in workflows

Connect Milvus to any app in workflows

Connect Milvus to any app in workflows

Milvus Integrations

Milvus triggers and actions

When to use Milvus

How to connect

Use in workflow automation

Frequently asked questions

What triggers does Milvus support?

What actions can I run in Milvus?

Do I need to write code to automate this?

Is the integration secure?

Milvus Integrations

Milvus triggers and actions

When to use Milvus

How to connect

Connect Milvus to any app in workflows

Use in workflow automation

Frequently asked questions

What triggers does Milvus support?

What actions can I run in Milvus?

Do I need to write code to automate this?

Is the integration secure?

Connect Milvus to any app in workflows

Connect Milvus to any app in workflows

Connect Milvus to any app in workflows