Make ↔ NetHunt CRM integration

Make scenarios create and update records in NetHunt CRM from your forms, shops and tables, and pick up new NetHunt records on a schedule to pass them on

NetHunt CRM lives next to your mail, and requests come from everywhere: website forms, a shop, a shared table, an ad form. Make is a platform that links such services with scenarios. The Make ↔ NetHunt CRM pair means we build and look after those scenarios for you: each request becomes a NetHunt record in the right folder without duplicates, changes reach the existing record, and new NetHunt records go on to the other tools your team uses. We connect to NetHunt through Make's built-in HTTP app and NetHunt's open documentation, not through a ready-made Make app for NetHunt. Below: what exactly moves, which scenarios we cover and which capabilities of both systems we rely on.

Request an integration System page: Make →System page: NetHunt CRM →

What moves between the systems

Make → NetHunt CRMA request that reaches a Make scenario from a form, a shop or a table is first searched for in NetHunt by email or phone, and only then created as a new record in the agreed folder.
Make → NetHunt CRMIf the person is already in NetHunt, the scenario updates the existing record with the new fields instead of creating a second one.
Make → NetHunt CRMSources that can send data the moment it appears start their scenario instantly through a Make address that receives the data; other sources are checked on a schedule.
NetHunt CRM → MakeOn a schedule, a Make scenario searches NetHunt for records added or changed in the agreed folders and passes them on: to a table, a mailing tool or a team chat.
NetHunt CRM → MakeThe list of NetHunt folders where the connected user may create records is read before each change, so a scenario never writes into a folder it only has viewing rights for.

What we connect

We list the sources and destinations with you: which forms, shops and tables send requests, which NetHunt folders receive them, and where new NetHunt records should go.
In NetHunt a separate user with rights only to the needed folders creates a personal access key; together with that user's email it is stored in the Make connection, not in the scenario text.
The scenarios run in your own Make account, so you see every run and its history; we build them there and hand over the description of each one.
We agree the schedule for each scenario and count how many operations it will use, because in Make every module run on every piece of data counts.
We test each scenario on a test folder in NetHunt with real requests, check duplicates with your team, then switch it to the working folders.

Automation scenarios

Requests copied from three places

Before a manager copies requests from the website form, the shop and an ad form into NetHunt by hand, and some are lost on busy days.

After each source has its scenario, and the request appears in the right NetHunt folder by itself.

Two records for one client

Before a client who writes twice gets two records, and two managers answer them.

After the scenario finds the existing record first and adds the new request to it.

The weekly list for the owner

Before someone exports new NetHunt records into a table every Monday.

After a scheduled scenario collects the new and changed records into the table on its own, and Monday starts with the numbers ready.

How it works technically

For those who want to check: each point links to the official documentation page it comes from.

By default a scenario runs every 15 minutes; the schedule is customizable, and the minimum interval depends on the plan.
Source: help.make.com ↗ checked 2026-09-27
Webhooks act as instant triggers: unlike scheduled triggers that periodically ask a service for new data, the scenario starts as soon as the webhook URL receives a request; custom webhooks accept any data.
Source: help.make.com ↗ checked 2026-09-27
The built-in HTTP app connects Make to API services and applications that have no ready integration with Make.
Source: apps.make.com ↗ checked 2026-09-27
NetHunt publishes open API documentation for developers, officially supporting listing folders and creating, searching and updating records.
Source: nethunt.com ↗ checked 2026-09-25
Sign-in combines the account's email with a personal access key, both encoded together as Basic authentication.
Source: nethunt.com ↗ checked 2026-09-25
A separate entry point lists only the folders where the user is allowed to create records, not just view them.
Source: nethunt.com ↗ checked 2026-09-25

Limits

The limits come from both systems. NetHunt officially documents listing folders and creating, searching and updating records; anything beyond that is not promised here. We rely on NetHunt's documentation and Make's built-in HTTP app, not on a ready Make app for NetHunt. NetHunt does not announce new records on its own in what we rely on, so the NetHunt-to-other-tools direction runs on a Make schedule; by default Make runs a scenario every 15 minutes, and the shortest interval depends on your Make plan. Every module run on every piece of data counts as an operation, so a scenario that handles many records at once is built to process them sparingly.

How to start

Three steps from a first message to work on your project.

01
Leave a request
Describe the task in the form — in text or by voice. Budget and timing are optional.
02
We review and estimate
A developer studies the brief, asks about anything unclear and sends an estimate.
03
We start
Once scope and price are agreed, the work begins.

Leave a request

or write to info@coreviaflow.space

Live project We built and run Gemalli — a B2B export platform with producer pages, a CRM and a deal chat. Read the case →

Questions

Whose Make account do the scenarios run in?

In yours. You see every run and its history, the operations are counted in your account, and the scenarios stay with you if you stop working with us.

Is there a ready NetHunt app in Make?

We do not build on one. The pair uses Make's built-in HTTP app, which Make offers for services without a ready integration, and NetHunt's open documentation. If a ready app fits your case better, we will say so.

How fast does a new NetHunt record reach the other tools?

On the next scheduled run, not instantly. We choose the interval with you, keeping in mind that more frequent runs use more operations.