Milvus and Ninox Integration
Keep Milvus and Ninox matched by integrating their events and actions. When database events happen in Milvus, update the Ninox automatically - without any line of code in visual workflow builder.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Milvus and Ninox
Detailed info you need to know about Milvus and Ninox integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Milvus to Ninox
Set up your Milvus and Ninox integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect Milvus and Ninox
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow[3]. No coding or API skills required.
STEP 2
Build a workflow
Paste selected Milvus and Ninox nodes onto the canvas[4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Milvus and Ninox. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between Milvus and Ninox work in WEXTL?
WEXTL exposes actions and triggers for Milvus and Ninox that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.
Milvus triggersNinox actions
Milvus modules
- Conduct a Query Finds entities in a Collection Name whose scalar fields match a Filter expression such as an ID list. Use Output Fields to trim what each entity returns and Partition Names to search only some partitions. Set Limit to cap results.
- Create a Collection Sets up a Collection Name with a vector field of a set Dimension, from 1 to 32768. Use Metric Type for the distance metric, and Primary Field and Vector Field to name the two fields. Add a Database Name to pick the database.
- Delete an Entity Deletes the entity with a matching ID from a Collection Name. Use Database Name to work in a database besides default.
- Describe a Collection Reads the schema and settings of one Collection Name. The result lists its Fields, Indexes, Partitions num, Shards num and Consistency level, among others.
- Drop a Collection Removes a Collection Name from its database and erases all the data in it. Set Database Name when the collection lives somewhere besides default.
- Get Entities Fetches entities from a Collection Name by their IDs, as one ID or a list in string or integer form. Use Output Fields to return only some fields, and Partition Names to read from specific partitions.
- Insert Entities into a Collection Adds up to 100 entities per request to a Collection Name. Use Data to send them, with keys that match the collection schema. Use Partition Name to insert into a specific partition instead of the default one. Responds with Insert count and Insert ids.
- List Collections Lists the collections of a database, which is default unless you use Database Name to name another. Use Limit to cap how many are returned.
- Make an API Call Sends a free-form request to the Milvus REST API, signed with your saved credential.
- Search Similarity in a Collection Runs a nearest-neighbour search on the vector field of a Collection Name, from a query Vector matching its dimension. Add a Filter to narrow candidates, or Search Parameters for Radius or Range Filter.
- Upsert Entities into a Collection Writes each entity from Data into a Collection Name, with keys that match its schema. The output reports the Upsert count and the Upsert ids.
- Watch Entities Checks on a schedule for newly created entities and runs the workflow once per entity found. Use Limit to set how many results one cycle works through.
- Watch Query Results A scheduled check that runs a query and triggers once for each result with a new ID. Raise Limit to let one cycle handle more results.
- Watch Vector Fields Polls on a schedule for vector fields created since the previous check, giving each its own run. Use Limit to control how many are worked with per cycle.
Ninox modules
- Create a Record Inserts a row in a Ninox table, with one input per field of the chosen Table. Use Extra Fields for references or multiple choice columns. Returns the new ID and Sequence.
- Create or Update a Record With an ID Writes a record to a Ninox table at one numeric Record ID. A free ID creates the record and an existing ID updates it. Extra Fields cover columns the form lacks.
- Delete a File Deletes one attachment from a record. Turn on Confirm to acknowledge that the file cannot be recovered afterwards.
- Delete a Record Deletes a record in a table. Switch Confirm on to confirm the call, because a deleted record cannot be undone.
- Delete Records Removes many records from a table in one request. Use Confirm to approve it, as the deletion is permanent.
- Download a File Fetches the content of an attachment on a record. Output holds the File, its File Name and Content Type.
- Find a Record Looks in a table for the first record whose fields equal every value of Filters. Use Choice Style to set how choice fields are returned.
- Get a Database Retrieves one Ninox database with its Settings, Schema and Version. Add the Schema Password for a password protected schema, otherwise Ninox answers with an encrypted schema.
- Get a Record Shows a single record of a table with its fields, Created At and Modified At. Use Choice Style to switch how choice fields are returned.
- Get a Table Pulls the definition of one table in a database, giving its ID, Name and Fields.
- Get a Team Finds one Ninox team and returns its ID and Name.
- List Database Changes Lists what changed anywhere in a database after a sequence number, taken from the seq of an earlier answer or of a record. The output holds Updates, Removes and the next Sequence.
- List Databases Shows the databases of a team, each with its ID and Name. Use Limit to set the maximum number of databases returned.
- List Record Files Shows the files attached to one record, each with its Name, Content Type, Size and Modified Date. Use Limit to cap how many files are returned.
- List Table Changes Lists the changes in one table made after a sequence number. Use Since Sequence to set where to start. Each result gives the Updates, the Removes and a fresh Sequence.
- List Tables Enumerates the tables inside a database with their ID, Name and Fields. Use Limit to decide how many tables come out.
- List Teams Retrieves Ninox teams, each with an ID and Name. Use Limit to bound the number of teams.
- Make an API Call Sends a free-form request to the Ninox REST API, signed with your saved credential.
- Run a Query Executes a read-only Ninox script against a database and returns its Result. Use Query to write the script, such as a select on one table.
- Run a Script Runs a Ninox script that may create, change or delete data and returns its Result. Turn on Confirm to run it, because the changes cannot be undone. On a private cloud the key needs the admin role.
- Search Records Returns records from a table, each as its own result. Narrow them with Filters or a Script Filter, sort with Order By, keep only those above an ID using Only After Record ID, and set Limit for the count.
- Update a Record Changes fields on a record that already exists. Use Clear Fields to empty fields, which wins over values filled in on the form, and Extra Fields for columns that form does not offer.
- Upload a File Adds a file to the attachments of a record. Map File from an earlier step such as a download or an email attachment, and use File Name to store it under another name.
- Watch New Records Polls a table on your schedule and fires for each record created since the last check. Use Limit to set how many of the newest records the first check takes.
- Watch Updated Records Checks a table on a schedule and fires for every record that was created or modified since the previous check. Use Limit to cap the newest records returned on the first check.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with Milvus and Ninox integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Milvus and Ninox.
References
List of sources used to gather information about the Milvus and Ninox integration.
- Milvus and Ninox integration source code, module specs and credentials implementation.
- Our Milvus and Ninox integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Milvus and Ninox, 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.
- Milvus integration information
- Ninox integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted Milvus and Ninox integration page documentation. Used sources, the role of AI, and how the team validates the result.

