Resources · Zapier integration

NetHunt CRM Zapier integrationAutomate NetHunt CRM with Zapier.

The NetHunt CRM Zapier integration gives you 8 triggers, 6 actions and 1 search. It follows records, comments, call logs and files in your folders, and lets your other tools create, update, delete or comment on records and attach Gmail threads.

See the 15 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the NetHunt CRM Zapier integration does for you

The NetHunt CRM Zapier integration connects NetHunt, the CRM that lives inside Gmail and Google Apps, to your other tools through Zapier. A Zap (the automation you build on Zapier: one trigger, then one or more actions) can react to what happens in your NetHunt folders and write records back into them.

Email conversations filed on the right record. A Gmail trigger such as New Email hands over a thread, Find Record locates the matching record, and Add Gmail Thread to Record attaches the conversation to it.

An alert when a deal reaches a stage. New or Updated Record in Filter watches one field, such as your pipeline stage, and the Zap tells the team in their chat tool when a record enters the filter you defined.

Leads that never land twice. A form or another tool sends a contact, and Create or Update Record either adds it to the folder or updates the existing record.

Every one of these runs through a NetHunt folder: all eight triggers and most actions ask you to pick one.

What Zapier does not do here: none of the eight triggers is instant, so each waits for Zapier's next check. New or Updated Record (Advanced) reports the change itself, not the full record, so getting the current version takes an extra search. See our n8n vs Zapier comparison.

Vocabulary

Zapier words, explained once

Eight words come back all over this page. Here they are, in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
Action
What the Zap does once it has started: the step that writes, sends or moves something on your behalf.
Task
The unit Zapier bills. Each action your Zap completes successfully counts as one task on your plan.
Polling vs instant
A polling trigger is checked by Zapier on a timer; an instant one is reported by the app as it happens. All NetHunt CRM triggers are polling ones.
Filter
A Zapier step that lets the Zap go on only when what arrived meets a condition you set, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can use what it found.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, and it then needs a paid plan.
Cost

What the NetHunt CRM Zapier integration costs you

NetHunt CRM is not a premium app on Zapier, so it works from the free plan. Zapier counts in tasks, never in checks.

  • Premium appNo, available on the free plan
  • Trigger check0 tasks
  • Successful action1 task each
  • Free plan100 tasks a month, two-step Zaps

The trigger costs nothing, however often Zapier looks at your folders. Each action that succeeds counts as one task, and one that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, capped at two steps. A filter, the Find Record search or a second action makes the Zap multi-step, which needs a paid plan. The interval below applies to all eight NetHunt CRM triggers. Every one of them is free to check.

Connect

Connect NetHunt CRM to Zapier in three steps

  1. 01

    Open your connections

    In your Zapier account, go to the Apps page and click + Add connection. A connection is your NetHunt account linked to Zapier once, then reused by every NetHunt step you add.

  2. 02

    Pick NetHunt CRM

    Type NetHunt CRM in the search box of the dialog, select it, then click Add connection. A new tab opens on the NetHunt side, where the sign-in happens.

  3. 03

    Sign in and grant access

    Sign in to NetHunt CRM in that tab and grant Zapier access to the account. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.

First Zap

Your first Zap: tell the team when a deal changes stage

GoalWhen a NetHunt record enters the stage you watch and meets your condition, post a message in your team chat.

  1. 01

    Pick the trigger

    Start a new Zap, choose NetHunt CRM and New or Updated Record in Filter. Set the Folder, the Field to watch (your stage field, for instance) and the Search Query.

  2. 02

    Test the trigger

    Run the test: Zapier brings back the three most recent matching records, so you map fields on a real one. If nothing comes back, check the query.

  3. 03

    Add a filter

    Add a Zapier filter with the field to look at, the rule and the value, to narrow the alert further. A filter makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add the message and publish

    Add your team chat as the action, write the message with the record details, test it, then click Publish to switch the Zap on.

Triggers

NetHunt CRM triggers on Zapier

8 events start a Zap when something happens in NetHunt CRM. Zapier checks for them at the interval your plan allows.

1

Deleted Record

Polling trigger

In Zapier“Triggers when a record gets deleted.”

Starts a Zap when a record is deleted from the NetHunt folder you choose. You keep a trace of what left the CRM somewhere else.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a deleted contact or deal should also be marked in a spreadsheet or another tool that mirrors your CRM.
Watch out
it only watches the one Folder you pick when you set it up, which is a required field.
2

New Call Log

Polling trigger

In Zapier“Triggers when a new record call log is created.”

Fires when a call log is added to a record in your chosen folder. Each logged call becomes an event the rest of the Zap can use.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when calls logged by the team should feed a report, a sheet or a follow-up task in another tool.
Watch out
the Folder is required, and only call logs on records in that folder are picked up.
3

New Comment

Polling trigger

In Zapier“Triggers when a new record comment is created.”

Picks up each new comment written on a record of the selected folder. Notes your team leaves in NetHunt can travel to the tools where others work.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a comment on a key account should reach your team's chat channel without anyone opening the CRM.
Watch out
a Zap that writes into the place its own trigger watches can start itself again. Test before you publish.
4

New File

Polling trigger

In Zapier“Triggers when a new file is added to a record.”

Kicks in when a file is added to a record in the folder you pick. Attachments on deals or contacts can then be copied, logged or announced.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a signed document added to a deal should be noted in a shared tracker.
Watch out
it reacts to files added to records, not to files elsewhere in your storage, and the Folder is required.
5

New Record

Polling trigger

In Zapier“Triggers when a new record is created.”

Watches a NetHunt folder for records created in it and passes each one to the next step.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when every new contact or company should also exist in your spreadsheet, newsletter list or billing tool.
Watch out
records imported in bulk can arrive as one huge batch, which Zapier's flood protection may hold back.
6

New or Updated Record (Advanced)

Polling trigger

In Zapier“Triggers each time a record is created, modified, or deleted. Provides the change type, author, time, 'from' and 'to' values. Requires a new record search to obtain an up-to-date record if necessary.”

Reports each creation, edit or deletion in a folder as a change: its type, who made it, when, and the values before and after. You get a change log rather than a record.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when you need an audit trail of who changed which value in the CRM.
Watch out
it does not carry the current record; add a Find Record step when the next action needs the up-to-date version.
7

New, Updated, or Deleted Record

Polling trigger

In Zapier“Triggers with an up-to-date record when it is created, modified, or deleted.”

Hands over the record as it currently stands each time it is created, changed or deleted in your folder. One trigger covers the three events.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to keep a copy of your CRM data in sync in another tool, whatever happened to the record.
Watch out
a Zap that writes into the place its own trigger watches can start itself over and over, so check at test.
8

New or Updated Record in Filter

Polling trigger

In Zapier“Triggers when a record matching a specific filter gets created or modified.”

Goes off when a record matching a search filter you write is created or changed. It is the trigger for pipeline moves, since you choose which field to watch.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a deal reaching a given stage should alert someone or start a follow-up.
Watch out
Field, Search Query and Folder are all required, and at least one field of the query must be the one picked in Field.
Actions

NetHunt CRM actions on Zapier

NetHunt CRM gives you 6 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Comment

Action

In Zapier“Creates new record comment.”

Writes a comment on a NetHunt record. It needs the Record and the Text of the comment.

When to use it
to leave on the record a note of what happened elsewhere, such as a ticket opened or an invoice sent.
Watch out
the Record ID comes from Find Record or Create Record.
2

Create Record

Action

In Zapier“Creates a new record.”

Adds a new record to the NetHunt folder you choose, filled with data from earlier steps. The Folder is the one required field.

When to use it
when a signup or a form entry should become a contact in your CRM.
3

Delete Record

Action

In Zapier“Deletes a record by a record ID.”

Removes a record from a NetHunt folder by its record ID. Folder and Record are required.

When to use it
when a contact removed from another system should also disappear from the CRM.
Watch out
the record to delete is named by its ID, which a Find Record step can supply.
5

Create or Update Record

Action

In Zapier“Creates a new record or updates an existing one.”

Creates a record in the chosen folder, or updates an existing one instead. The Folder is the required field.

When to use it
for leads that can come back through several forms, so they land on one record rather than many.
Watch out
check at test which record it updated before you publish.
6

Update Record

Action

In Zapier“Updates a record by a record ID.”

Changes an existing record, identified by its record ID, in a given folder. Folder and Record are both required.

When to use it
when a payment or a signed contract in another tool should change a field on the deal.
Watch out
get the Record ID from a Find Record step or a Create Record action earlier in the Zap.
Searches

NetHunt CRM search on Zapier

1 search step looks for data that already exists in NetHunt CRM, so a later step can use it.

A search step looks up a record that already exists, so the next steps can use it. In the action list, searches sit at the bottom under SEARCH. It adds a step, so a Zap with a search needs a paid plan. Three settings decide what happens when the result is not a single clean match.

1

Find Record

SearchFind or create

In Zapier“Finds a record by ID or text query.”

Looks for a record in the chosen folder, by its ID or by a text query. The Folder is required. In the editor you will also see Find or Create Record: it is this same search with the creation box ticked, not a separate operation.

When to use it
before Update Record, Create Comment or Add Gmail Thread to Record, which all need a Record ID.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there. Switched on, the Zap carries on without a result.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into a find-or-create: it drops the setting above and asks for the fields needed to create the missing record.
  3. If multiple search results are found?
    Keep the first match (the default), stop the Zap, or hand every match on at once.
When it breaks

When the NetHunt CRM Zap breaks

Zapier links no help article to NetHunt CRM, so the known weak spots are the general ones of any Zap.

Four of them matter for a CRM. If a Zap stops doing what you expect, our Zapier troubleshooting guide is the next stop.

  • Nothing from before the Zap

    A Zap only reacts to what happens after it is switched on. Records already in your folders are not picked up, and moving that history is a separate job.

  • A Zap that sets itself off

    A Zap that writes into the very place its own trigger watches can start itself again and again, and burns through your tasks fast.

  • A big batch held back

    When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back.

  • The same record never runs twice

    On a polling trigger, Zapier keeps track of what it has already seen, so the same item does not start the Zap a second time.
Need help

Need help automating NetHunt CRM with Zapier?

A person reads every message.

FAQ

NetHunt CRM Zapier integration: questions people ask

01Is the NetHunt CRM Zapier integration free?
Yes, within the free plan's limits. NetHunt CRM is not a premium app, so you can use it without a paid Zapier plan. The free plan gives 100 tasks a month and as many Zaps as you like, each capped at two steps: one trigger and one action. Find Record adds a step, as does a filter or a second action, so any Zap using them needs a paid plan. New Record followed by a spreadsheet row stays within the free plan.
02How many Zapier tasks does a NetHunt CRM Zap use?
One task for each action that succeeds, and nothing for the trigger. Zapier can check your folders as often as your plan allows without spending a task. A Zap that copies each new record to a sheet costs one task per record. A Zap that finds a record and then attaches a Gmail thread to it runs two steps after the trigger, and Add Gmail Thread to Record counts as one task. An action that fails is not counted against your plan.
03Does NetHunt CRM trigger Zaps in real time?
No. All eight NetHunt CRM triggers are polling triggers. Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one, 2 minutes on Professional, 1 minute on Team and Enterprise. On the paid plans you can change how often a polling trigger checks, and run a check by hand from the editor. A deal that changes stage just after a check waits for the next one.
04What does it take to connect NetHunt CRM to Zapier?
An account on NetHunt CRM, plus read or write access on anything you do not own yourself and want the Zap to touch. Start from the Apps page of your Zapier account with + Add connection, pick NetHunt CRM, sign in in the tab that opens and grant Zapier access. Every trigger and most actions then ask you to pick a Folder when you set them up. The connection itself is set once.
05Why does New or Updated Record in Filter need a Search Query?
Because the trigger only fires on records that match a filter you write, and that filter is the Search Query. It goes with two other required fields: the Folder and the Field to monitor, such as your stage field for pipeline moves. At least one field used in the query must be the one picked in Field. Run the test after writing the query and check that the records coming back are the ones you expect.
06What if the NetHunt CRM operation you need is not there?
Check the NetHunt CRM page on Zapier, which shows the current list of triggers, actions and searches. Today that is 8 triggers, 6 actions and 1 search. Several gaps close by chaining steps: Find Record then Update Record to change a record you only know by name, or Find Record after the Advanced trigger to get the current version. When no chain fits, the job needs another route than the steps NetHunt CRM offers on Zapier.
07Zapier, Make or n8n for NetHunt CRM?
It depends on what you weigh most. On Zapier, NetHunt CRM brings 15 operations, eight polling triggers and billing per successful action. If your Zaps mostly copy records to other tools in two steps, the free plan is a fair start. Chains like Find Record then Update Record need a paid plan, so compare how each platform bills a run with several steps, how often it checks for changes, and whether it exposes the NetHunt operations you need.
Same platform

Other docs you might need on this stack.

Browse all integrations