Resources · Make integration

NocoDB Make integrationAutomate NocoDB with Make.

Your NocoDB tables can update themselves. The NocoDB Make integration brings 12 modules, the bricks you chain into an automated scenario, plus 2 triggers that start it. Here is the plain version: what each one does, and which scenario to build first.

Try the NocoDB integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the NocoDB Make integration actually do?

The NocoDB Make integration is a bridge between your NocoDB bases and every other app you use. You link your account once, that link is your connection, and 12 modules are then available inside a scenario, the automation Make runs for you: 2 triggers to start it, 6 actions to write, and 4 searches to look things up.

Three jobs come back on every project. A support team watches its intake table with Watch Records, then pushes each new line where the work happens. An online store keeps stock in NocoDB, so Search Records finds the right row and Update a Record writes the quantity left. An agency imports a batch of leads with Bulk Create Records, then tidies the whole batch with Bulk Update Records.

What Make will not do here: the 12 modules all work at row level. Creating a table, adding a column or changing a view is not in the list. The module documentation published for this app is generated from the NocoDB docs too, so a detail can be wrong, and anything that matters gets checked against NocoDB itself. When a module is missing, Make an API Call reaches the rest of the API with the same connection.

NocoDB also exists on the n8n side, worth saying out loud. To pick one, there is the n8n vs Make comparison and the NocoDB n8n integration page, which shows the same moves with the other tool. And when a scenario has to run for a whole team rather than one person, that is what the Make agency page is about.

Connect

How do you connect your NocoDB account to Make?

  1. 01

    Create an API token in NocoDB

    The token comes from NocoDB, not from Make. Open the user menu at the bottom left of the sidebar, go to Account Settings, then the Tokens tab. Click Add New API Token, give it a name, save, and copy the token under the Actions menu.

  2. 02

    Add your first NocoDB module

    In Make, drop any NocoDB module into a scenario and click Create a connection. If the module carries the instant tag, Make asks for Create a webhook first, then Create a connection. The Connection name field is optional.

  3. 03

    Paste your credentials

    Paste the token you copied, add the API IDs of the base and tables you want to reach, and follow what the window asks. Once the connection answers, every NocoDB module reuses it, and Make can list what lives in your base.

First scenario

Your first scenario: a new row becomes a record

GoalWhen a row is created or updated in NocoDB, Make reads it and writes a record in the table you choose.

  1. 01

    Create the scenario

    From the Scenarios page, start an empty scenario and click the + in the middle of the canvas. Every module gets added through that button, and the first one you drop is the one that starts everything.

  2. 02

    Add Watch Records

    Search NocoDB by name, pick Watch Records, and link your account with Create a connection if you have not done it yet. The module then asks which table it should keep an eye on.

  3. 03

    Check the date field

    Watch Records needs a Created Time or Last Modified Time field in that table to tell what is new. If it is missing, add it in NocoDB before going further, or the trigger sees nothing.

  4. 04

    Add Create a Record behind it

    Click the + on the right of the trigger and add Create a Record. Pick the destination table, then drag the values coming from the first module into the fields you want filled.

  5. 05

    Test with Run once, then switch it on

    Click Run once, the button that runs the scenario a single time, and read what each module received. If the row lands where it should, set the schedule on the first module, every 15 minutes out of the box, and turn the scenario on.

Triggers

What can start a NocoDB scenario?

2 modules start a scenario when something happens in NocoDB. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by NocoDB as soon as it happens.

NocoDB1Watch Records

Watch Records

Scheduled trigger

In Make“Returns all newly created or updated records in a table (requires "Created Time" or "Last Modified Time" fields).”

Watch Records keeps an eye on one table and hands your scenario every row that was just created or changed. Each row arrives as a bundle, the single item that travels to the next module.

How it fires
scheduled, which means Make goes and looks instead of being told. Make checks the app on the scenario's schedule, and the shortest gap is 15 minutes on the Free plan.
When to use it
your team fills an intake table by hand, and everything after it should start without anyone clicking.
Watch out
the table needs a Created Time or Last Modified Time field, otherwise the module cannot tell what is new.
NocoDB2Watch Responses

Watch Responses

Instant trigger

In Make“Triggers when a new response is submitted.”

Watch Responses starts the scenario the moment a new response is submitted in NocoDB, with nobody opening Make.

How it fires
instant. The app calls Make through a webhook, an address Make creates for NocoDB to ping as soon as it happens, so there is no interval to wait for.
When to use it
a request drops in and someone is waiting on the answer, where the delay of a scheduled check would show.
Watch out
an instant module needs its webhook before anything else. Click Create a webhook, then Create a connection, in that order.
Modules

What the 10 other NocoDB modules do

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

NocoDB1

Create a Record

Action

In Make“Creates a record in the given table.”

Create a Record writes one new row in the table you point at, with the values mapped from the modules before it.

When to use it
a form answer, a paid order or a fresh ticket has to land in the base where your team follows it.
Watch out
it never checks whether the row is already there, so a scenario that runs twice writes twice. Upsert a Record is the one that looks first.
NocoDB2

Delete a Record

Action

In Make“Deletes a record with the given record ID.”

One row, one record ID, and Delete a Record takes it out of the table for good.

When to use it
a duplicate slipped in, or the test lines have to disappear once your scenario works.
Watch out
nothing in Make brings the row back. Run the scenario with Run once on a copy of the table before you let it loose on the real one.
NocoDB3

Get a Record

Action

In Make“Gets a record by the record ID.”

Get a Record pulls one row back by its record ID, with all its fields, ready for the rest of the scenario.

When to use it
a later module only carries an ID and you need the rest of the line, a name, a status, an amount.
Watch out
it works on an ID and nothing else. With an email or a reference in hand, Search Records comes first.
NocoDB4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call opens the rest of the NocoDB API to your scenario. Same connection, any endpoint the API exposes, a request you write yourself.

When to use it
what you need is not in the other modules of this app, and rebuilding the whole thing elsewhere makes no sense.
Watch out
Make sends exactly what you type, so the NocoDB API reference stays open next to the editor.
NocoDB5

Update a Record

Action

In Make“Updates a record by record ID.”

Update a Record changes the fields you name on a row that already exists, found by its record ID. The rest of the line stays untouched.

When to use it
a status moves from pending to done, a delivery date shifts, a comment comes back from another tool.
Watch out
no ID, no update. Put it behind a trigger or behind Search Records, the two modules that hand you one.
NocoDB6

Upsert a Record

Action

In Make“Tries to update a record with the given record ID, if the record does not exist, it creates one.”

Upsert a Record decides for you. It tries the update first on the record ID you give, and creates the row when there is nothing to update.

When to use it
a list that keeps coming back, a catalogue you refresh without ending up with two copies of every line.
Watch out
the decision rests on the ID you send. Send a wrong one and you get a brand new row instead of the correction you wanted.
NocoDB7

Bulk Create Records (Advanced)

Search

In Make“Сreates multiple records.”

Bulk Create Records writes a whole set of rows in one pass, instead of one module run per line.

When to use it
an import lands at once, a batch of leads or a product list.
Watch out
it is typed as a search, so it can send several bundles on, and each one costs an operation, the unit Make counts on your plan.
NocoDB8

Bulk Delete Records (Advanced)

Search

In Make“Delete multiple records.”

Bulk Delete Records clears several rows in a single move, once you have told it which ones.

When to use it
a batch of test lines, or rows already processed, has to leave the table in one go.
Watch out
the danger sits upstream. Whatever the module before it hands over gets deleted, so read that list with Run once before this module is even connected.
NocoDB9

Bulk Update Records (Advanced)

Search

In Make“Updates multiple records.”

Bulk Update Records rewrites the same fields across a group of rows, one pass for the lot.

When to use it
a whole batch changes status together, invoices marked as sent, contacts retagged after a campaign.
Watch out
the rows have to be identified before the module runs, so Search Records usually sits right in front of it.
NocoDB10

Search Records

Search

In Make“Returns a list of records matching the where condition.”

Search Records goes through a table and returns the rows matching the condition you write, ready for the modules that follow.

When to use it
you hold an email, a reference or a status, and the record ID you need is somewhere in the base.
Watch out
a search gives back zero, one or several rows, never a guaranteed single one. Plan for the empty case, and keep in mind that every row found runs the rest of the scenario again.
Need help

Need help automating NocoDB with Make?

A person reads every message.

FAQ

Questions that come up next

01Is the NocoDB Make integration free?
Yes. NocoDB is a standard app in Make, so it is available from the Free plan and there is nothing extra to pay on the Make side for this app. The plan is where the limits show up: 2 active scenarios, 15 minutes minimum between two scheduled runs, 5 minutes of run time per execution, files up to 5 MB and 512 MB of transfer. Paid plans drop the gap to 1 minute, lift the cap on active scenarios and push run time to 40 minutes. What your NocoDB account costs is settled on the NocoDB side.
02What do you need to connect NocoDB to Make?
An active NocoDB account, an API token, and the API IDs of the base and tables you want to reach. The token is created inside NocoDB: user menu at the bottom left, Account Settings, Tokens tab, Add New API Token, then copy it from the Actions menu. In Make, add any NocoDB module, click Create a connection, name the connection if that helps you, and paste the credentials. Instant modules ask for Create a webhook first. The connection is made once and every NocoDB module reuses it.
03Does the NocoDB trigger react in real time?
It depends which one you pick. Watch Records is scheduled: Make checks the table on the scenario's schedule, which means 15 minutes minimum on the Free plan and one minute on a paid one. Watch Responses is instant: NocoDB calls Make through a webhook as soon as a response is submitted, and the scenario starts right there. If the reaction has to be immediate, the instant trigger is your module. If a regular pass is enough, Watch Records takes fewer steps to set up, since there is no webhook to create.
04What if a NocoDB module is missing in Make?
Make an API Call is the way out for this app. It borrows the same connection and reaches any endpoint the NocoDB API exposes, so whatever the other modules leave out still gets handled inside the same scenario. Two caveats. You write the request yourself, which means the NocoDB API reference stays open beside you. And the module documentation published for this app is generated from the NocoDB docs, so a detail can be wrong: check anything important against NocoDB directly.
05Make or n8n for NocoDB?
It depends on who will maintain the thing. Make gives you a visual editor where modules are chained one to the next, a Free plan to try it, and NocoDB available as a standard app. n8n has a NocoDB node as well, so the same job can be built there. The useful question is who opens that scenario a year from now: pick the tool that person can read. The comparison linked above walks through the criteria without choosing a winner for you.
Hack'celeration Lab

Get our weekly automation tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations