Resources · Make integration

Noloco Make integrationAutomate Noloco with Make.

Can Make keep your Noloco records moving without code? Yes. The Noloco Make integration gives you 7 modules: 2 scheduled triggers, 4 actions and 1 search. This guide is for ops teams running a Noloco app and takes you from connection to a first working scenario.

Try the Noloco integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Noloco Make integration do for you?

The Noloco Make integration links your Noloco account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules. A module is one brick of that chain, such as a trigger, an action or a search. Noloco brings 7 of those bricks, so records can be watched, created, updated, found or deleted without opening Noloco.

A client portal that fills itself. When a form tool or a CRM hands Make a new client, Create a Record adds it to the right Noloco collection, and Search Records can check first that this client is not already there. Each item travelling between modules is a bundle: one client, one row.

Follow-up work that starts on its own. Watch New Records spots a fresh request in Noloco and passes it along, for example to create a task record in another collection. Watch Record Updates does the same when someone edits a record, which suits approval flows where a status moves forward.

Clean data without manual edits. Update a Record corrects a record you already know by its ID, and Delete a Record removes one for good. For requests the ready-made modules do not cover, Execute a GraphQL Query sends a query you write yourself.

What Make does not do here: both triggers are scheduled, so Make checks Noloco on the scenario's schedule instead of hearing about changes the moment they happen. The official doc also warns that it was AI-generated from Noloco's documentation, so confirm critical details with Noloco. Weighing your options? Read n8n vs Make, check Make pricing, or get hands-on with Make training.

Connect

How do you connect Noloco to Make?

  1. 01

    Add a Noloco module

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

  2. 02

    Copy your API key

    In Noloco, open the settings panel, go to Integrations & API Keys and copy the key shown in the API Keys section. You need an active Noloco account for that key to exist.

  3. 03

    Paste it and save

    Back in Make, type a name in Connection name if you want one (it is optional), paste the API key and save. Make can now read your Noloco data and list what each module can work on.

First scenario

Your first scenario with Noloco and Make

GoalWhen a new record lands in Noloco, Make creates a matching follow-up record in another collection.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the editor. That empty circle is where your first module goes.

  2. 02

    Add Watch New Records

    Search for Noloco, pick Watch New Records and link your account. Once the connection exists, Make lists what it can read in Noloco, so you simply choose where new records should be watched.

  3. 03

    Add Create a Record

    Click the + on the right of the trigger and add Create a Record. Pick the target collection, then map data from the new record into the fields of the follow-up record.

  4. 04

    Test with Run once

    Add a test record in Noloco, then click Run once. Read the bundles each module received and confirm the follow-up record landed in the collection you expected.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule: every 15 minutes by default, down to 1 minute on paid plans. Then switch the scenario on so it keeps working without you.

Triggers

What can start a Noloco scenario?

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

Noloco1Watch New Records

Watch New Records

Scheduled trigger

In Make“Watches for newly created records.”

Watch New Records hands your scenario the records newly created in Noloco, one bundle per record, ready to feed the modules that follow.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and never more often than every 15 minutes on the Free plan.
When to use it
a new client request or order entered in your Noloco app should set off work elsewhere, such as a welcome message or a task.
Watch out
records show up at the next check, not the second they are saved, so do not promise instant replies to the people adding them.
Noloco2Watch Record Updates

Watch Record Updates

Scheduled trigger

In Make“Watches for newly updated records.”

Watch Record Updates picks up the records someone edited in Noloco and sends each one to your scenario, so a changed status can set off the next step.

How it fires
scheduled. Make checks the app on the scenario's schedule; on paid plans the gap between two runs can drop to 1 minute.
When to use it
an approval flow where a manager moves a request to approved in Noloco and the requester should hear about it.
Watch out
if the same scenario then runs Update a Record on the watched records, its own edits come back as updates. Write the result to another collection instead.
Modules

What else can Make do in Noloco?

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

Noloco1

Create a Record

Action

In Make“Creates a new collection record.”

Create a Record adds a new entry to a Noloco collection from data another module passed along, so your app fills up without anyone typing.

When to use it
a signed quote or a fresh lead from another tool should appear in your Noloco client list.
Watch out
nothing blocks duplicates by itself; run Search Records first when the same person may arrive twice.
Noloco2

Delete a Record

Action

In Make“Deletes an existing collection record.”

Delete a Record removes an existing Noloco record for good, which keeps collections clear of cancelled or test entries.

When to use it
an order gets cancelled in your shop and its Noloco record should disappear with it.
Watch out
a deletion cannot be undone from Make, so try the module on a test record with Run once before switching the scenario on.
Noloco3

Execute a GraphQL Query

Action

In Make“Performs an arbitrary authorized GraphQL query.”

Execute a GraphQL Query sends a query you write yourself to Noloco, through the connection you already set up, for the moments when the ready-made modules stop short.

When to use it
you need a request that the create, update, delete and search modules do not offer.
Watch out
the query is written by hand, so it suits someone at ease with GraphQL; check the answer with Run once before relying on it.
Noloco4

Update a Record

Action

In Make“Updates an existing record by ID.”

Update a Record changes an existing Noloco record identified by its ID, so a status, an owner or an amount stays current without manual edits.

When to use it
a payment confirmed in another tool should mark the matching Noloco invoice as paid.
Watch out
the module needs the record ID; get it from Search Records or from a Noloco trigger placed earlier in the scenario.
Noloco5

Search Records

Search

In Make“Search for a record by an of its unique values.”

Search Records finds a Noloco record from one of its unique values and hands it to the next module, so later steps work on the record you actually mean.

When to use it
right before an update or a deletion, to fetch the record you actually mean.
Watch out
a search can return zero, one or several bundles; when nothing matches, the modules after it have nothing to work on.
Need help

Need help automating Noloco with Make?

A person reads every message.

FAQ

Noloco and Make: common questions

01Is the Noloco Make integration free?
Yes. Noloco is a standard app in Make, so it is available from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios no more often than every 15 minutes, stops a run after 5 minutes, handles 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 per run. Make counts operations, meaning one module run on one bundle. You still need an active Noloco account with its own subscription.
02What do you need to connect Noloco to Make?
An active Noloco account and its API key. In Noloco, open the settings panel, go to Integrations & API Keys and copy the key shown in the API Keys section. In Make, add any Noloco module, click Create a connection, give it a name if you like, then paste the key. That connection is reused by all 7 Noloco modules, so you do this once per account. No webhook is involved, because none of the Noloco modules is instant.
03Do Noloco triggers in Make fire in real time?
No. Watch New Records and Watch Record Updates are both scheduled triggers: Make checks Noloco on the scenario's schedule instead of being alerted by Noloco. A new scenario runs every 15 minutes by default, the Free plan cannot go below 15 minutes, and paid plans can go down to 1 minute. A record created or edited in Noloco therefore reaches your scenario at the next check, not the moment it is saved. Plan your flows around that gap, especially anything a customer is waiting on.
04What if a Noloco module is missing in Make?
Start with Execute a GraphQL Query. It sends a query you write to Noloco through your existing connection and covers requests that the create, update, delete and search modules do not handle. Noloco has no generic Make an API Call module in Make, so this GraphQL module is the way in. If writing GraphQL is not your thing, another app in the scenario may already hold the data you need, or an automation specialist can write the query with you. The doc lists no specific limits for Noloco, so check edge cases with Noloco directly.
05Make or n8n for Noloco?
It depends on your criteria, not on a winner. In Make, Noloco comes with 7 modules: 2 scheduled triggers, 4 actions including a GraphQL query, and 1 search, all usable from the Free plan and assembled visually in a scenario you can test with Run once. The same app often has an n8n node too, so look at that side before choosing and compare the modules each tool offers for your exact flow. If your other automations already run in Make, Noloco slots into the same editor with a single connection.
Same platform

Other docs you might need on this stack.

Browse all integrations