Resources · Make integration

Nanonets Make integrationAutomate Nanonets with Make.

Can Make manage your Nanonets models without a line of code? The Nanonets Make integration gives you 6 modules: 3 actions and 3 searches, no trigger. This guide is for teams that already use Nanonets and want to connect it, then build a first scenario step by step.

Try the Nanonets integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Nanonets Make integration do for you?

The Nanonets Make integration links your Nanonets account to Make, a visual tool where you chain apps together without code. Inside a scenario (the automation you build in Make), Nanonets modules create OCR models, fetch one model by its ID and list the image classification or object detection models you already have.

A new OCR model when a request comes in. Someone on the operations team fills a form to ask for a new document type. Make picks up that entry from the other app and runs Create a New OCR Model, so nobody has to open Nanonets by hand to start the model.

An up to date register of your models. List Image Classification Models and List Object Detection Models return every model of each kind as separate bundles (one item per model), ready to be written into a table. The Airtable Make integration is a common destination for that kind of register.

A check on one specific model. When a process only needs one model, Get OCR Model by ID or Get a Object Detection Model by ID reads that model and passes its data to the next module.

Know the limits before you start. Nanonets has no trigger in Make, so a scenario starts from another app or from a schedule. None of the six modules is named for sending a file to a model; for any endpoint the list does not cover, Make an API Call reuses the same connection. To decide between tools, the n8n vs Make comparison lays out the criteria, and the Make review describes the editor in detail.

Connect

How do you connect your Nanonets account to Make?

  1. 01

    Copy an API key from Nanonets

    In Nanonets, open the left panel of the Extract Data screen, click Account Info, then API Keys. Click Add a New Key and copy the key that appears on screen. You need an active Nanonets account for this.

  2. 02

    Add a Nanonets module in Make

    Log in to Make, open your scenario and add any Nanonets module. Click Create a connection. A connection is your Nanonets account linked to Make once, then reused by every Nanonets module you add later.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like; the field is optional. Paste the API key you copied, or follow the instructions Make shows, and save. The module fields then unlock.

First scenario

Build your first scenario with Nanonets

GoalWhen a new request lands in another app, Make creates an OCR model in Nanonets.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Nanonets has no trigger, so pick the app where requests arrive, such as your form or spreadsheet tool.

  2. 02

    Set the starting module

    Choose the module of that other app that watches new entries and connect its account. Every entry it finds becomes a bundle, one item that flows to the next module.

  3. 03

    Add Create a New OCR Model

    Click the + on the right of the first module, search for Nanonets and pick Create a New OCR Model. Click Create a connection and paste your API key.

  4. 04

    Map the request data

    Fill the fields Make shows for the module. Where a value should come from the request, click the field and pick it from the data of the first module instead of typing it.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received. Check in Nanonets that the new model is there before you go further.

  6. 06

    Schedule and switch on

    Open the clock on the first module: a new scenario runs every 15 minutes by default. Adjust Scheduling if you need to, then switch the scenario on.

Modules

What each Nanonets module does in Make

Nanonets gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Nanonets1

Create a New OCR Model

Action

In Make“Creates a new OCR model.”

This action sets up a fresh OCR model in your Nanonets account straight from a scenario, so a new document type can get its own model the moment someone asks for it.

When to use it
a request from another app, such as a form entry or a new row, should open a model without anyone logging in to Nanonets.
Watch out
each run creates another model, so test with Run once before switching the scenario on.
Nanonets2

Get a Object Detection Model by ID

Action

In Make“Retrieves an object detection model by ID.”

Hand it the ID of an object detection model and you get back that one model, ready for the next module to use. It saves you browsing Nanonets to find a model you already know.

When to use it
the ID is already stored somewhere, in a table or a previous module, and you need that model's details.
Watch out
it only covers object detection; for OCR models, use Get OCR Model by ID.
Nanonets3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

When none of the other five modules matches what you need, this one lets you call any endpoint of the Nanonets API with the connection you already set up. Nothing new to authorize.

When to use it
your process needs a Nanonets operation that no listed module is named for.
Watch out
you write the request yourself, so keep the Nanonets API documentation open while you build it, and test with Run once.
Nanonets4

Get OCR Model by ID

Search

In Make“Searches for a model.”

You get back a single OCR model and its data, which lets a scenario check a model before doing anything else with it. Make treats it as a search: it can return nothing if the ID matches no model.

When to use it
a table keeps the IDs of your OCR models and a scenario needs to read one of them.
Watch out
plan what happens when the search comes back empty, or the following modules have nothing to work with.
Nanonets5

List Image Classification Models

Search

In Make“Lists all image classification models.”

Pulls every image classification model from your account, one bundle per model, which gives you a complete picture without opening Nanonets at all.

When to use it
you want a register of classification models in a spreadsheet or database that the whole team can read.
Watch out
each model becomes its own bundle, so every module placed after it runs once per model and uses one operation each time (an operation is what Make counts on your plan).
Nanonets6

List Object Detection Models

Search

In Make“Lists all object detection models.”

Returns all your object detection models, each as a separate bundle, so a scenario can go through them one by one or copy them to another tool.

When to use it
you need an inventory of detection models, or the IDs to feed into Get a Object Detection Model by ID.
Watch out
image classification models are not included; add List Image Classification Models if you want both kinds in the same register.
Need help

Need help automating Nanonets with Make?

A person reads every message.

FAQ

Nanonets and Make: common questions

01Is the Nanonets Make integration free?
Yes, on the Make side. Nanonets is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution at most per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in credits per month. Your Nanonets subscription is separate and depends on Nanonets itself.
02What do you need to connect Nanonets to Make?
An active Nanonets account and an API key. To get the key, open the left panel of the Extract Data screen in Nanonets, click Account Info, then API Keys, then Add a New Key, and copy the key shown on screen. In Make, add any Nanonets module, click Create a connection, name the connection if you want to, and paste the key. That single connection then serves all six Nanonets modules of your scenarios.
03Does the Nanonets Make integration react in real time?
No, because Nanonets has no trigger in Make: none of its six modules can start a scenario on its own. You start the flow another way. Either you put a trigger from another app first, for example the tool where requests arrive, or you run the scenario on a schedule. A new scenario runs every 15 minutes by default, and the Free plan does not go below that interval. Paid plans can go down to 1 minute.
04What if a Nanonets module you need is missing in Make?
Use Make an API Call. This module calls any endpoint of the Nanonets API with the connection you already created, so it covers operations the other five modules do not, such as anything outside creating, reading or listing models. You write the request yourself, based on the Nanonets API documentation. Test it with Run once and read the bundle it returns before you connect further modules. For errors you cannot explain, the Make documentation for Nanonets also invites you to contact Nanonets directly.
05Should you use Make or n8n for Nanonets?
It depends on where the rest of your processes already run. In Make, Nanonets comes with 6 modules, including Make an API Call, and works from the Free plan inside a visual editor where each module is a bubble on a canvas. If your team already builds its automations in n8n, check whether a node for Nanonets covers your need there before you switch tools. The deciding factors are the modules available for your case and the tool your team already knows.
Same platform

Other docs you might need on this stack.

Browse all integrations