NetHunt CRM and Zapier: what syncs, what doesn't, and how to set it up
Zapier connects NetHunt CRM to other apps with 8 triggers, 6 actions and 2 searches on every NetHunt plan. Triggers poll for changes, every 15 minutes on Zapier's Free plan.
- Connector
- Zapier app listing for NetHunt CRM, connected with a NetHunt API key. NetHunt documents the setup and hosts the API endpoints behind it.
- Sync direction
- Two-way: NetHunt CRM records trigger Zaps, and Zaps create, update and delete NetHunt CRM records
- Setup time
- Not stated in the docs; the setup is 7 steps and an API key
- Availability
- Zapier integration is included on all NetHunt plans (Basic, Basic+, Business, Business+, Custom); Zapier plan requirements not confirmed in the docs I read
- Our rating
- 4 out of 5. Eight triggers, six actions and two searches on every NetHunt plan; triggers poll every 15 minutes on Zapier's Free plan.
| What | Direction | Detail |
|---|---|---|
| New records | NetHunt CRM → Zapier | The New Record trigger fires when a record is created in the folder you choose. Every trigger requires a folder. |
| Changed and deleted records | NetHunt CRM → Zapier | Four triggers cover this: Deleted Record, New, Updated, or Deleted Record, New or Updated Record in Filter, and an Advanced one that returns change type, author, time and from/to values. |
| Comments, call logs and files | NetHunt CRM → Zapier | Separate triggers fire on a new record comment, a new call log and a new file added to a record. The API docs describe the files as Google Drive files. |
| Create and update records | Zapier → NetHunt CRM | Actions are Create Record, Update Record and Create or Update Record. The first two use fields mapped from the trigger app. |
| Find records | Zapier → NetHunt CRM | Find Record searches by ID or text query. Find or Create Record creates a record when the search returns nothing. |
| Comments and deletions | Zapier → NetHunt CRM | Create Comment adds a comment to a record. Delete Record removes a record by its ID. |
| Gmail threads on records | Zapier → NetHunt CRM | Add Gmail Thread to Record links an email conversation from Gmail to a NetHunt record. |
Setting it up
- In NetHunt CRM, open Settings, then Apps and other integrations, and copy your API key.
- Log in to Zapier, or create an account, and start a new Zap.
- Choose NetHunt CRM as the trigger app, or as the action app if another tool starts the Zap.
- Connect the account: enter the Gmail address where NetHunt CRM is installed, and paste the API key.
- Choose the NetHunt folder, such as Contacts or Companies. Every trigger and action asks for one.
- Test the trigger. For an action, map the fields from the trigger app to the NetHunt fields.
- Publish the Zap. A Zap does nothing until it is on.
Where the integration stops
- Triggers poll, they don't push. The Zapier listing says Zapier checks for new data every 15 minutes on the Free plan. It states no interval for paid plans, so check Zapier's plan page.
- Related records need a Record ID. Mapping a company name into a Related field returns an HTTP 500 error. Add a Find Record step and map its Record ID, as NetHunt's help article describes.
- Call logs only trigger. The Zapier listing shows no action that creates a call log. The NetHunt API page documents a call-log endpoint, so check that route if you need to write them.
- API rate limits depend on the NetHunt plan. Basic allows 5,000 calls a day and 60 a minute. The pricing page does not say whether Zapier calls count against these.
- Country fields use two-letter ISO codes. The API docs give "GB" as the format, so clean country names before they reach NetHunt.
Zapier connects NetHunt CRM to other apps without code. It suits teams that want form, sheet or ad-platform data in NetHunt, or NetHunt changes passed to another tool. The Zapier listing offers 8 triggers, 6 actions and 2 searches. NetHunt CRM includes the integration on every plan.
The fact that surprises teams: every NetHunt trigger polls. The Zapier listing says Zapier checks for new data every 15 minutes on the Free plan. A new NetHunt record does not reach the next app at once.
Triggers cover more than new records
NetHunt records can start a Zap in eight ways. Besides new and deleted records, there is a trigger for records matching a filter. The Advanced trigger returns the change type, the author, the time and the before and after values.
Comments, call logs and files each have their own trigger. A call logged in NetHunt can post to another tool without any change to the record.
Actions write records, but linking needs an extra step
Zapier writes to NetHunt through Create Record, Update Record and Create or Update Record. It can also add a comment, delete a record by ID, and link a Gmail thread to a record. Two searches, Find Record and Find or Create Record, avoid duplicates.
The common failure is the Related field. NetHunt's help article explains that Zapier needs the Record ID of the related record. Most source apps send only a name, and the step returns an HTTP 500 error.
The fix is a Find Record step on the related folder, searching by name. Map its Record ID into the Related field. NetHunt's article walks through this for a contact linked to a company.
For Gmail threads, see NetHunt CRM and Gmail. The Zapier action only links a thread by its Gmail ID.
Connection depends on your Gmail account and API key
NetHunt runs inside Gmail, so Zapier asks for the Gmail address where NetHunt is installed. It also asks for an API key from Settings. Each Zap uses one folder, so plan one Zap per folder and event.
API limits scale with the plan. Basic allows 5,000 calls a day and 60 a minute. The pricing page does not say whether Zapier calls count against those limits.
For other Zapier connections, see the Zapier integration page.