Resources · Make integration

NoCodeTable Make integrationAutomate NoCodeTable with Make.

Can Make keep your NoCodeTable records up to date on its own? The NoCodeTable Make integration gives you 6 modules: 5 actions and 1 search. This guide is for people who know their tables but are new to Make, and it walks you from the connection to a first working scenario.

Try the NoCodeTable integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the NoCodeTable Make integration let you automate?

The NoCodeTable Make integration links your NoCodeTable account to Make so a scenario, the automation you build in Make, can write, read, change and remove records for you. It has no trigger of its own, so another app or a schedule starts the scenario, and NoCodeTable modules do the work on your records.

Every signup lands as a record. A form tool or a CRM starts the scenario, and Create a Record writes the answer into NoCodeTable. Nobody retypes anything, and each person shows up as one clean row.

Existing rows get corrected instead of duplicated. Search Records looks for the person first, by whatever your table uses to tell rows apart, then Update a Record changes the row it found. This is the pattern to learn if the same contact can come back twice.

Old entries leave the table on a clear rule. A search picks the records that match a condition, and Delete a Record removes them. Test this one carefully, because a deleted record does not come back.

What Make does not cover: Make itself says its documentation for NoCodeTable is limited, because there is not enough public information about the app. So the page stays with what the module names tell you, and Make an API Call is the way to reach anything the 5 other modules leave out. Before you start, the Make review explains how the editor works, and the Make pricing page tells you what each plan includes. If you also look at n8n, the n8n vs Make comparison sets the two tools side by side.

Connect

How do you connect NoCodeTable to Make?

  1. 01

    Add a NoCodeTable module

    In your scenario, click the +, search for NoCodeTable and pick any of its modules, for example Create a Record. Then click Create a connection. A connection is your NoCodeTable account linked to Make once, and every NoCodeTable module reuses it.

  2. 02

    Name the connection

    This step is optional but helps later. Give the connection a name that says which account it is, such as the workspace or the client it belongs to. When several people share one Make team, a clear name avoids picking the wrong account.

  3. 03

    Authorize Make and save

    Follow what NoCodeTable asks for: either approve Make on the NoCodeTable page that opens, or paste the key NoCodeTable gives you. Click Save. From then on, Make can list what your account lets it read when you fill a module.

First scenario

Your first scenario with NoCodeTable

GoalWhen a new answer comes in from another app, Make looks for that person in NoCodeTable and updates their record.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the app that receives the answer first, your form or your CRM, since NoCodeTable has no trigger of its own.

  2. 02

    Add Search Records

    Click the + on the right of the first module and choose Search Records. Create the connection, then map a value from the previous module that identifies the person, such as an email if your table stores one. Make only lists what your table really holds.

  3. 03

    Add Update a Record

    Add Update a Record after the search. Map the record the search found, then the values to change. Each bundle, meaning one item passing from one module to the next, updates one record.

  4. 04

    Test with Run once

    Click Run once and send a test answer. Read the bundles each module received, and check in NoCodeTable that the right record changed and only that one.

  5. 05

    Schedule and switch it on

    If the first app's trigger is a scheduled one, set its schedule (every 15 minutes by default); an instant trigger needs no schedule. Then switch the scenario on. Each module run on a bundle is an operation, the unit Make counts on your plan.

Modules

What the NoCodeTable modules do

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

NoCodeTable1

Create a Record

ActionIn the docs only

You get a new record in NoCodeTable built from data another app just sent, without typing it yourself. Map each value from the previous module and Make writes it in one go.

When to use it
a lead, an order or a signup arrives elsewhere and must become a row in your table.
Watch out
it always adds a new record, so run Search Records first if the same person can come back.
NoCodeTable2

Delete a Record

ActionIn the docs only

This one takes a record out of your NoCodeTable table so your list only keeps what still matters. It acts on a single record, usually one that a search found just before.

When to use it
a customer cancels, a test entry needs to go, or a row has been copied somewhere else.
Watch out
a deletion cannot be undone from Make, so test on a dummy record with Run once before you switch the scenario on.
NoCodeTable3

Get a Record

ActionIn the docs only

Hand it the reference of one record and it returns that record's content, ready to feed the next module. Pick it over a search when the scenario already knows exactly which record it wants.

When to use it
a previous step gave you the record's reference and you need its other values for an email or a document.
Watch out
without a valid reference it has nothing to fetch, so map it from an earlier module rather than typing it.
NoCodeTable4

Make an API Call

ActionIn the docs only

Reach any part of the NoCodeTable API that the 5 other modules do not cover, with the same connection you already created. It is the fallback when the module you want is missing from the list.

When to use it
you need an operation of NoCodeTable that none of the ready-made modules offers.
Watch out
you write the request yourself, so keep the NoCodeTable API reference open while you set it up.
NoCodeTable5

Search Records

SearchIn the docs only

Find the records that match what you are looking for, then pass each one down the scenario as a separate bundle. It is the step that tells you whether a person or an item is already in your table.

When to use it
before creating, updating or deleting, to find the right row by an email or a reference.
Watch out
the search can return zero, one or several records, and every module after it runs once per record found.
NoCodeTable6

Update a Record

ActionIn the docs only

Change the values of a record that already exists, so your table follows what happens in your other tools. Only the record you point to is touched.

When to use it
a deal changes status, an address is corrected, or a payment is confirmed in another app.
Watch out
it needs to know which record to change, so place Search Records or Get a Record right before it and map the record from there.
Need help

Need help automating NoCodeTable with Make?

A person reads every message.

FAQ

Questions about the NoCodeTable Make integration

01Is the NoCodeTable Make integration free?
Yes, NoCodeTable is a standard app, so you can use it on the Make Free plan. That plan has limits worth knowing: 2 active scenarios, at least 15 minutes between two scheduled runs, up to 5 minutes 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 runs of up to 40 minutes. Usage is counted in operations, and each one is simply a single module running on a single bundle.
02What do you need to connect NoCodeTable to Make?
You need a NoCodeTable account and a Make account. Make's documentation lists no special prerequisite for this app. You add any NoCodeTable module, click Create a connection, optionally name it, then either authorize Make on the NoCodeTable page or paste the key NoCodeTable gives you, and click Save. The connection is created once and every NoCodeTable module in your scenarios reuses it, so you do not repeat the process for each module.
03Does the NoCodeTable Make integration react in real time?
Not by itself, because NoCodeTable has no trigger module in Make. You start the scenario another way. The first option is a trigger from another app, such as a form or a CRM, with NoCodeTable modules placed after it. The second is a schedule set on the first module, every 15 minutes by default for a new scenario, or as low as 1 minute on a paid plan. Whether the start is immediate then depends on the trigger of that other app.
04What if a NoCodeTable module you need is missing in Make?
Use Make an API Call. It lets a scenario reach any endpoint of the NoCodeTable API with the connection you already have, so it covers what Create a Record, Get a Record, Search Records, Update a Record and Delete a Record leave out. Keep in mind that Make says its documentation for NoCodeTable is limited, since little public information exists about the app. You will need the NoCodeTable API reference to build the request yourself.
05Should you use Make or n8n for NoCodeTable?
It depends on the tool your team already uses. On Make, NoCodeTable comes with 6 modules and a generic API call, and this page shows how to use them. The same app often exists on n8n too, but this page does not check what an n8n node for NoCodeTable would offer. Compare the concrete operations each tool gives you for your use case, and read the n8n vs Make comparison linked earlier on this page for the general criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations