Resources · Make integration

NetHunt Make integrationAutomate NetHunt with Make.

Can your CRM update itself while reps sell? The NetHunt Make integration offers 14 modules: 4 triggers that watch records, calls, comments and files, plus actions and searches. Sales and ops teams will find here how to connect the account and build a first scenario.

Try the NetHunt integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the NetHunt Make integration do for a sales team?

The NetHunt Make integration links your NetHunt CRM account to Make, a no-code tool where you build scenarios: automations made of modules, each module being one step such as watching records or creating a comment. Make checks NetHunt on the scenario's schedule and hands each new item, called a bundle, to the next module.

Every web lead lands as a NetHunt record. Your form tool passes its answers to Make, Create a Record opens the record, and Create a Comment adds what the lead wrote so the rep reads it before calling back.

Calls logged elsewhere reach the CRM. When your phone system reports a finished call, Create a Record Call Log attaches it to the matching record, found beforehand with List Records. The other way round, Watch Call Logs spots each call entered in NetHunt and can copy it to a reporting sheet.

Deal changes stay visible. List Updated Records returns the records edited since a time you set and says which fields moved, a clean base for a digest sent to a sales manager.

The Make docs for NetHunt give no quota or size limit, and they warn that their content is AI-generated from NetHunt's documentation: check any detail that matters with NetHunt. What the listed modules skip goes through Make an API Call, with the same connection. Many apps also exist as an n8n node; the n8n vs Make comparison lays out how the two tools differ, and the Make training takes you past this first scenario.

Connect

How do you connect NetHunt to Make?

  1. 01

    Copy your API key and email

    In NetHunt CRM, click your profile icon at the top right, open Settings, then the API Key section. Copy the key shown there and note the email address of your profile: the connection uses both.

  2. 02

    Add a NetHunt module

    In your Make scenario, add any NetHunt module and click Create a connection. A connection is your NetHunt account linked to Make once; every NetHunt module of the scenario reuses it afterward.

  3. 03

    Paste the credentials

    The Connection name field is optional, but a clear name such as “NetHunt sales” helps when several accounts coexist. Paste the API key and the email you copied, or follow the on-screen instructions, then save.

First scenario

Your first NetHunt scenario: from web form to CRM record

GoalWhen a form in another app receives a new lead, Make creates the NetHunt record and adds a comment with the lead's message.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the module of the app that collects your leads, such as your form tool, and connect that account.

  2. 02

    Add Create a Record

    Click the + on the right of the form module, search for NetHunt and choose Create a Record. Click Create a connection and paste your API key and email.

  3. 03

    Map the lead's answers

    Fill the module with the form answers: click a field, then pick the matching value from the previous module. Once connected, Make lists what it can read in NetHunt, so you pick instead of typing.

  4. 04

    Add the comment

    Click the + again and add Create a Comment. Point it at the record Make just created, then map the message the lead left in the form as the comment text.

  5. 05

    Test with Run once

    Send a test entry through your form, then click Run once. Open the bubble above each module to read the bundle it received, and look for the new record in NetHunt.

  6. 06

    Schedule and switch on

    Open the clock on the first module: a new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Keep or change the schedule, then switch the scenario on.

Triggers

What can start a NetHunt scenario?

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

NetHunt1Watch Call Logs

Watch Call Logs

Scheduled trigger

In Make“Triggers when a new call log has been created.”

Each call your team logs in NetHunt turns into a bundle that Make can forward, so call activity leaves the CRM without anyone copying it by hand. The trigger picks up call logs newly created in NetHunt.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, so a call appears at the next check rather than the second it is logged.
When to use it
feeding a sheet where a sales manager follows call activity per rep.
Watch out
every call log is one bundle, and each module after the trigger spends one operation per bundle.
NetHunt2Watch Comments

Watch Comments

Scheduled trigger

In Make“Triggers when a new comment has been added within a specific folder.”

Notes your colleagues leave on a deal can reach a chat channel or a task list: this trigger reports new comments added in one NetHunt folder, which you pick when you set it up.

How it fires
scheduled. Make checks the app on the scenario's schedule and asks for the comments added since then; nothing reaches the scenario between two checks.
When to use it
account managers discuss a client in the CRM and the delivery team needs those notes where it works.
Watch out
it only reports comments added after the scenario starts; to read the ones already there, use List Comments.
NetHunt3Watch Google Drive Files

Watch Google Drive Files

Scheduled trigger

In Make“Triggers when Google Drive file has been created.”

A new Google Drive file can start a scenario too: the trigger reacts when NetHunt reports a newly created Google Drive file and passes it on as a bundle, ready to be logged or shared.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a file shows up at the next check.
When to use it
keeping a list of the proposals and contracts added for your clients, or telling a teammate a document is ready.
Watch out
the docs describe this trigger in one line, so run it once with a test file and read the bundle before mapping anything.
NetHunt4Watch Records

Watch Records

Scheduled trigger

In Make“Triggers when a new record has been created.”

A fresh record in NetHunt becomes the starting point of your automation: the trigger catches newly created records and hands their data to the modules that follow, for a welcome email, a task or a row in a sheet.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default on a new scenario.
When to use it
a new client in the CRM should open onboarding tasks in your project tool.
Watch out
if the same scenario also runs Create a Record, each record it creates can start it again; keep creation in a separate scenario.
Modules

What can Make do in NetHunt?

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

NetHunt1

Create a Comment

Action

In Make“Creates a comment.”

Leave a note on a NetHunt record from another app, so the context of a deal sits where your reps read it. The text can come from any earlier module of the scenario.

When to use it
after a support ticket closes or a quote is signed, to keep a trace on the client record.
Watch out
point the comment at the right record; when you only know the client's name, find the record first with List Records.
NetHunt2

Create a Record

Action

In Make“Creates a record.”

A new client, lead or company lands in NetHunt with no typing at all: this action builds the record from data that another app already holds.

When to use it
a signup form, a booking or an online order that should open a CRM record.
Watch out
look the contact up with List Records before creating it, or a returning client ends up twice in your CRM.
NetHunt3

Create a Record Call Log

Action

In Make“Creates a record call log.”

Calls made outside NetHunt get written into the client's history, so the record tells the whole story. The action adds one call log to one record.

When to use it
your calling tool reports a finished call and you want it next to the deal rather than in a separate app.
Watch out
the log belongs to a single record; when the calling tool does not know which one, find it first with List Records.
NetHunt4

Get a Record

Action

In Make“Gets a record.”

Bring the full details of one record into the scenario when you already know which one you need. The result is a single bundle you can map in the next modules.

When to use it
a trigger gave you the record's reference and you need its other details before drafting an email or a document.
Watch out
without that reference, start with List Records, which can return several records.
NetHunt5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Whatever the other modules leave out stays within reach: this action calls any endpoint of the NetHunt API, reusing the connection you already set up.

When to use it
a need that none of the listed modules covers, once you know which endpoint answers it.
Watch out
you write the request yourself, so test it with Run once before plugging other modules after it.
NetHunt6

Update a Record

Action

In Make“Updates a record.”

Keep a record current when something changes elsewhere: this action edits an existing NetHunt record with new values coming from the scenario.

When to use it
a quote signed in your e-signature tool should move the matching deal forward in the CRM.
Watch out
map only the fields you mean to change, and try it on a sample record with Run once before switching the scenario on.
NetHunt7

List Call Logs

Search

In Make“Lists all call logs.”

Pull the call logs stored in NetHunt in one go, each log becoming its own bundle for the modules that follow, outside any new-call event.

When to use it
preparing a call report for a pipeline review with the sales team.
Watch out
a search returns zero, one or many bundles, and every module placed after it runs once per bundle, which adds operations to your plan.
NetHunt8

List Comments

Search

In Make“Lists all comments.”

Read back the comments already written in NetHunt, to archive them, export them or sum up what was said about an account.

When to use it
before a handover between two account managers, to gather the notes left so far.
Watch out
each comment arrives as a separate bundle; to send them in one message, group them first with an aggregator module.
NetHunt9

List Records

Search

In Make“Retrieves a list of all records in a specific folder.”

Load every record of a chosen NetHunt folder into the scenario, to spot a contact before creating it or to mirror a folder in a spreadsheet.

When to use it
checking whether a client already exists before Create a Record runs.
Watch out
the module reads one folder at a time and returns all its records, so a large folder means many bundles and many operations downstream.
NetHunt10

List Updated Records

Search

In Make“Lists records which updated since the time specified and shows what fields were updated.”

Find out what changed in NetHunt since a time you choose: the module returns the edited records and shows which fields were modified.

When to use it
a change digest for a manager, or syncing only the edited deals to another tool instead of the whole CRM.
Watch out
choose the starting time with care; set too early, it brings back changes you already handled.
Need help

Need help automating NetHunt with Make?

A person reads every message.

FAQ

NetHunt and Make: common questions

01Is the NetHunt Make integration free?
Yes, on the Make side. NetHunt is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes per run, with usage counted in credits each month. On the NetHunt side, you still need an active NetHunt CRM account under its own subscription.
02What do you need to connect NetHunt to Make?
An active NetHunt CRM account, its API key and the email address of your profile. In NetHunt, open your profile menu at the top right, go to Settings, then to the API Key section, and copy the key. In Make, add any NetHunt module, click Create a connection, give it a name if you like, and paste the key and the email. The connection is created once and every NetHunt module of your scenarios reuses it, so you will not repeat the step for each module.
03Do the NetHunt triggers in Make fire in real time?
No. All four NetHunt triggers are scheduled: Make checks NetHunt on the scenario's schedule and processes what it finds at that moment. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; paid plans go down to 1 minute. NetHunt has no instant trigger in Make, the kind an app fires through a webhook as soon as something happens. If waiting for the next check is a problem, shorten the schedule on a paid plan.
04What if a NetHunt module is missing in Make?
Use Make an API Call. This module reaches any endpoint of the NetHunt API with the connection you already have, so a need not covered by the 14 modules does not require a new setup. You write the request yourself and check the answer with Run once before adding modules after it. Keep in mind that the NetHunt page of the Make docs is AI-generated from NetHunt's own documentation and lists no limits, so confirm important behavior with NetHunt before relying on it.
05Should you use Make or n8n for NetHunt?
It depends on your own criteria. This page covers Make, where NetHunt comes with 14 ready modules, including 4 scheduled triggers, plus Make an API Call for the rest. Many apps also have an n8n node, so check whether NetHunt is listed there before deciding. Then weigh what matters for your team: the modules your use case needs, the tool your other automations already run on, and who will keep the scenarios up to date. No ranking or cost comparison between the two tools is made here.
Same platform

Other docs you might need on this stack.

Browse all integrations