Mindee and Ninox Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Connect Mindee to Ninox on visual integration builder following simple steps below. When ai event fired from Mindee, it will run actions inside Ninox app - exactly how you set them in your database automation. No coding skills required.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Mindee and Ninox

Detailed info you need to know about Mindee and Ninox integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Mindee

    • AI
    • 2 searches
    • 5 actions

    Document AI platform that extracts structured data from invoices, receipts, and forms.[5]

  • Ninox

    • Database
    • 2 triggers
    • 14 searches
    • 9 actions

    Low-code database and workflow platform.[6]

How to connect Mindee to Ninox

Set up your Mindee and Ninox integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Mindee and Ninox work in WEXTL?

WEXTL exposes actions and triggers for Mindee 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.

Ninox triggersMindee actions

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.

Mindee modules

  • Get a Resume Prediction Collects the prediction for a resume queued earlier, using the Job ID from Parse a Resume. Output covers the Inference and N Pages.
  • Get Custom Document Results Collects the parsing result of a custom Mindee API job, using its Job ID and the Mindee Account Username / API Name / Version of that API. Returns the Inference.
  • Make an API Call Calls the Mindee REST API directly with a free-form request under your saved credential.
  • Parse a Custom Document Queues a Document for parsing by your own Mindee API, found through Mindee Account Username / API Name / Version. Returns a Job ID and Status to follow up on.
  • Parse a Receipt Reads a receipt Document with the expense receipt parser from Mindee and returns the Inference and Is Rotation Applied.
  • Parse a Resume Queues a resume or CV Document for parsing, returning the Job ID, Status and Available at. Pass the Job ID to Get a Resume Prediction.
  • Parse an Invoice Runs a Document through the invoice parser in Mindee and returns the extraction as Inference, without queuing a job.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Mindee and Ninox integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Mindee and Ninox on WEXTL®

Claim your 3-day trial to build Mindee with Ninox integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Mindee and Ninox.

How do I connect Mindee and Ninox?

Connect your Mindee and Ninox accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Mindee and Ninox?

Example: when the "Watch New Records" trigger in Ninox fires, WEXTL can "Get a Resume Prediction" in Mindee. Mindee has 7 actions (including Get a Resume Prediction, Get Custom Document Results, and Make an API Call). Ninox has 23 actions (including Create a Record, Create or Update a Record With an ID, and Delete a File). Add filters and transforms between steps when you need them.[1]

Can Mindee trigger actions in Ninox, and Ninox in Mindee?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Mindee and Ninox?

No. Mindee-to-Ninox automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Mindee integrate with Ninox in real time?

Yes. Trigger-based automations start the moment Mindee (or Ninox) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Mindee + Ninox integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Mindee with Ninox?

You can build your Mindee + Ninox automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Mindee and Ninox integration.

  1. Mindee and Ninox integration source code, module specs and credentials implementation.
  2. Our Mindee and Ninox integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Mindee and Ninox, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Mindee integration information
  6. Ninox integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Mindee and Ninox integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Mindee and Ninox, or get started