Resources · Make integration

Ninox Make integrationAutomate Ninox with Make.

What if every new Ninox record could start its own follow-up work? The Ninox Make integration gives you 16 modules: one instant trigger, 10 actions and 5 searches. This guide shows how to link your database, build a first scenario and pick the right module for each job.

Try the Ninox integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Ninox Make integration do for you?

The Ninox Make integration links your Ninox databases to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, searches or acts in one app. Ninox can alert Make the moment a record is created or updated, and Make can then read, write or file data back into your tables.

React when a record changes. Watch Record Events receives each created or updated record as a bundle, one item passed from module to module. From there, Create Record can open a matching entry in a follow-up table, or Update Record can stamp a status on another record.

Keep documents next to the data. Upload File To A Record attaches a file to the right record, List Files From Record tells you what is already attached, and Download File From Record hands a file to the next step when another app needs it.

Find the right record before acting. Look Up Record finds an entry from the details you already have, and List Database Table Records walks through a whole table, one bundle per record. Each module run on each bundle is one operation, the unit Make counts on your plan.

One limit comes from the Make documentation: Ninox can be slow to load data, and that delay can end in a timeout on the Ninox side. The Make troubleshooting guide covers how to read those errors. If you are still choosing a tool, the n8n vs Make comparison lays out the criteria, and Make training walks you through the editor from scratch.

Connect

How do you connect Ninox to Make?

  1. 01

    Generate an API key in Ninox

    Log in to Ninox, click the cog wheel in the top right corner and choose Zapier Integrations in the menu. Click Generate to get your API key, then copy it to your clipboard.

  2. 02

    Open the connection dialog in Make

    In your scenario, add any Ninox module and click Create a connection. A connection is your Ninox account linked to Make once, then reused by every Ninox module you add later.

  3. 03

    Paste the key and confirm

    Paste the API key into the dialog and click Continue. Make now lists the teams, databases and tables it can read, so you pick them from a menu instead of typing names by hand.

First scenario

Your first scenario: log every new Ninox record in a follow-up table

GoalWhen a record is created in a Ninox table, Make creates a matching record in a follow-up table.

  1. 01

    Start the scenario with the trigger

    On the Scenarios page, create a new scenario and click the +. Search for Ninox, pick Watch Record Events and copy the webhook address Make gives you.

  2. 02

    Wire the trigger inside Ninox

    In Ninox, open the table to watch, click the cog wheel above it and choose Edit fields.... Open Trigger on create, switch to Text view, paste the code and replace the placeholder URL with your webhook address.

  3. 03

    Choose the data Ninox sends

    Still in the trigger field, pick the variables you want Make to receive from the menu on the left, then click OK. Only those values will reach the scenario.

  4. 04

    Add Create Record

    Back in Make, click the + on the right of the trigger and add Create Record. Choose the follow-up table and map the values that came from the trigger into its fields.

  5. 05

    Test with Run once, then switch it on

    Click Run once, then create a test record in Ninox. Check the bundles each module received. When the new entry shows up in the follow-up table, switch the scenario on.

Triggers

What starts a Ninox scenario?

1 module starts a scenario when something happens in Ninox. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Ninox as soon as it happens.

Ninox1Watch Record Events

Watch Record Events

Instant trigger

In Make“Receive events when records have been created or updated.”

Watch Record Events starts your scenario as soon as a record is created or updated in the Ninox table you chose, and passes along the values you picked in Ninox. You get one bundle per event, ready to map into the next module.

How it fires
instant. Ninox calls Make through a webhook the moment the change happens, so there is no interval to set.
When to use it
any flow that should follow a change in Ninox, such as a new order entered by the sales team.
Watch out
the setup happens in Ninox, not only in Make. You paste the webhook address into the Trigger on create or Trigger after update field, in Text view.
Modules

What else can Make do with Ninox?

Ninox gives you 15 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Follow these steps to set up the trigger:

1 module

Open the table you want to watch for created and/or updated records.

Click on the cog-wheel above the table and select the Edit fields... option.

Now you can see the Trigger on create and Trigger after update fields. Click on one of the fields.

Switch from Visual view to Text view.

Go to Make and add the Watch Record Events module to your scenario.

Copy the provided webhook address.

Go back to the Ninox trigger settings and replace the https://paste-your-webhook-url.here with the copied webhook address.

Enter the data you want to send to the Make module (select variables from the menu on the left) and click the OK button.

Ninox1

Paste the following code to the field:

ActionIn the docs only

This entry is not a module you drag into a scenario. It is the step of the trigger setup where you paste the webhook code into the Ninox trigger field, so that Ninox knows where to send its events.

When to use it
right after you copy the webhook address from Watch Record Events, while the Ninox field is open in Text view.
Watch out
replace the placeholder https://paste-your-webhook-url.here with your own address, or Make receives nothing.

Other modules

14 modules
Ninox2

Create Record

Action

In Make“Creates a new record in a table.”

Create Record adds a new entry to the Ninox table you pick. Its fields are filled with values mapped from earlier modules, so a form answer, an order or a contact from another app becomes a proper row.

When to use it
when data starts outside Ninox and should end up inside it without anyone retyping it.
Watch out
if the trigger watches the same table, each new record can start the scenario again. Write to a different table.
Ninox3

Delete File From Record

Action

In Make“Deletes a file from a Ninox record.”

Delete File From Record removes one attached file from a Ninox record and leaves the record itself untouched. Handy for cleaning up a draft once the signed version has arrived.

When to use it
after you have replaced a document with Upload File To A Record and the old copy only adds noise.
Watch out
run List Files From Record first so you target the right file, and test on a sample record before going live.
Ninox4

Delete Record

Action

In Make“Deletes a single record.”

Delete Record removes a single record from a table. It keeps Ninox tidy when a duplicate, a cancelled request or a test entry should disappear as part of the flow.

When to use it
at the end of a flow that has already copied or archived the data elsewhere, once the original is no longer needed.
Watch out
treat the deletion as final. Place a filter before this module and try it on a test record with Run once first.
Ninox5

Download File From Record

Action

In Make“Downloads a file attached to a record”

Download File From Record fetches a file attached to a Ninox record and passes its content to the next module. That is what lets another app store, send or read the document.

When to use it
when a contract or a photo kept in Ninox must travel to a storage tool or an email step.
Watch out
on the Free plan, Make handles files up to 5 MB, so a large scan can stop the run.
Ninox6

Get Record

Action

In Make“Returns a single record given the ID of it.”

Get Record returns one Ninox record when you already know its ID, with all its values available for mapping. It is the direct route when an earlier step has handed you that ID.

When to use it
after Watch Record Events, if you sent the record ID with the trigger data and need fields you left out.
Watch out
without an ID, this module has nothing to work with. Use Look Up Record to find the entry from other details instead.
Ninox7

Look Up Record

Action

In Make“Returns a record based on the information you provide.”

Look Up Record finds a Ninox record from the information you give it, like an email address or a reference. You get back the entry you were looking for, with its ID ready for the next step.

When to use it
before an update, when the other app knows a customer by email and not by Ninox ID.
Watch out
plan the path for no match. Add a filter so the following modules only run when a record came back.
Ninox8

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you reach any endpoint of the Ninox API from your scenario, with the connection you already set up. It covers whatever the listed modules leave out.

When to use it
when none of the other Ninox modules does the exact job you need and the Ninox API offers it.
Watch out
you write the request yourself, so keep the Ninox API reference open while you fill it in, then check the response with Run once.
Ninox9

Update Record

Action

In Make“Updates a record.”

Update Record changes the values of an existing Ninox record, so a status, an amount or a date stays in sync with what happened elsewhere. Your team sees the new value without touching the database.

When to use it
when a payment clears or a ticket closes in another tool and the matching record should reflect it.
Watch out
updating a table watched through Trigger after update fires the scenario again. Avoid that loop with a filter or a separate table.
Ninox10

Upload File To A Record

Action

In Make“Uploads files to a Ninox record.”

Upload File To A Record attaches a file to a Ninox record, so the document lives right next to the data it belongs to. Invoices, photos and signed forms land in the correct entry automatically.

When to use it
when a file arrives from email, storage or a form tool and belongs to a specific customer or project.
Watch out
find the target record first with Look Up Record, since the upload needs to know which entry receives the file.
Ninox11

List Databases

Search

In Make“Lists all databases within a team.”

List Databases returns every database inside a Ninox team, one bundle per database. It gives you a clear view of what the connection can reach before you go further.

When to use it
when a flow has to handle several databases of the same team rather than one you pick by hand.
Watch out
each database found becomes its own bundle, and every module placed after it runs once per bundle, which costs operations.
Ninox12

List Database Table Records

Search

In Make“Lists all records of the specified table.”

List Database Table Records pulls all the records of the table you choose, each one arriving as its own bundle. It turns a whole Ninox table into material for the rest of the scenario.

When to use it
to copy a table to another tool, or to check every entry against a rule and update the ones that fail.
Watch out
a large table means many bundles and many operations, and slow Ninox loading can end in a timeout.
Ninox13

List Database Tables

Search

In Make“Lists all the tables in a database.”

List Database Tables shows every table in a Ninox database, one bundle each. It helps when a scenario must find its way through a database whose structure you do not want to hard-code.

When to use it
ahead of List Database Table Records, when the flow must visit several tables in turn.
Watch out
it returns the tables, not their records, so another module still has to read the data inside them.
Ninox14

List Files From Record

Search

In Make“Lists files associated with the record. Does not download the file, just information about the files.”

List Files From Record tells you which files are attached to a record, without downloading any of them. You get their details, which is enough to decide what happens next.

When to use it
before Download File From Record or Delete File From Record, to pick exactly the file you mean.
Watch out
it returns information only. To move the actual document to another app, add Download File From Record after it.
Ninox15

List Teams

Search

In Make“Lists all your teams.”

List Teams returns all the Ninox teams your account belongs to, one bundle per team. It is the first rung when a scenario needs to go from team to database to table on its own.

When to use it
in a setup that spans several Ninox teams, such as one team per client, before List Databases.
Watch out
the list depends on the account behind the API key, so a team you cannot see in Ninox will not appear here.
Need help

Need help automating Ninox with Make?

A person reads every message.

FAQ

Ninox and Make: common questions

01Is the Ninox Make integration free?
Yes. Ninox is a standard app in Make, so it is available on the Free plan along with the rest of the standard catalog. The Free plan has limits you will feel as you grow: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations each month.
02What do you need to connect Ninox to Make?
You need a Ninox account and an API key, and the Make documentation lists no other prerequisite. In Ninox, click the cog wheel in the top right corner, open Zapier Integrations and click Generate. Copy the key, then in Make open the Create a connection dialog of any Ninox module, paste it and click Continue. The same connection then serves every Ninox module in your scenarios, so you only do this once per account.
03Does the Ninox trigger in Make fire in real time?
Yes. Watch Record Events is an instant trigger: Ninox calls Make through a webhook as soon as a record is created or updated, so there is no polling interval to wait for. The catch is the setup. You copy the webhook address from Make, then paste code into the Trigger on create or Trigger after update field of the table in Ninox, in Text view, and choose which values to send. Once that is saved and the scenario is on, each change reaches Make right away.
04What if a Ninox module you need is missing in Make?
Use Make an API Call. It sends any request the Ninox API supports, with the connection you already have, so you are not limited to the 15 other modules. If the problem is speed rather than a missing feature, know that Ninox can take a while to load data and that the delay can end in a timeout; that issue sits on the Ninox servers, not in your scenario. The Make troubleshooting guide on the site explains how to read that kind of error when it shows up in a run.
05Should you use Make or n8n for Ninox?
It depends on the tool your team already uses and how it likes to build. In Make, Ninox comes with 16 modules, including an instant trigger for created or updated records, file handling and Make an API Call for anything else. Many apps also have an n8n node, so check whether the Ninox side you need exists there before deciding. Compare the two on the modules you actually need for your flow, not on reputation, and pick the editor your team will keep maintaining.
Same platform

Other docs you might need on this stack.

Browse all integrations