A new client writes on Instagram
Before a manager notices the message later and copies it into NetHunt by hand.
After the message lands in NetHunt linked to the client record on its own.
CRMUANetHunt CRM integration & automation
The CRM that lives inside Gmail: client folders, messages and mail stay connected without leaving your inbox
NetHunt is built directly inside Gmail, with client folders working like a pipeline instead of a separate app you have to open. It already connects to Gmail and the wider Google Workspace, to WhatsApp and Instagram messages, and to team chat in Slack, plus a wide range of other tools through a connecting service. We link NetHunt to whatever a ready connection doesn't cover, so a client record updates itself wherever it needs to, without anyone re-typing it.
What we connect
- Client records in folders (NetHunt's version of a pipeline) are created, found and updated automatically — nobody types the same client into two places.
- Gmail and the wider Google Workspace connect directly, so an email thread with a client stays attached to their card instead of living only in the inbox.
- Messages from WhatsApp and Instagram land in NetHunt already linked to the right client, instead of staying stuck in a separate messaging app.
- A change on a client's record can reach your team in Slack the moment it happens, instead of someone remembering to write a manual update.
- Through a connecting service such as Zapier, NetHunt can pass a change on to many other tools at once, without a separate custom build for each one.
- For steps none of the ready connections cover, we build a custom link, so a folder record, an email or a message stays tied to the same client everywhere.
Automation scenarios
An email thread with a client keeps growing
Before a manager forwards important emails into the CRM by hand, and some get missed.
After the Gmail thread stays attached to the client card automatically, so anyone who opens it sees the full history.
A folder record changes
Before teammates in Slack find out about a client update only when someone remembers to mention it.
After the update can reach the team in Slack the moment the record changes.
A tool outside the ready connections needs client data
Before someone exports records into a spreadsheet by hand and re-imports them elsewhere.
After a connecting service such as Zapier passes the update onward automatically instead.
How it works technically
For those who want to check: each point links to the official documentation page it comes from.
NetHunt publishes open API documentation for developers, officially supporting listing folders and creating, searching and updating records.
Source: nethunt.com ↗ checked 2026-09-25The interaction happens over HTTPS using GET and POST methods, with data sent as JSON.
Source: nethunt.com ↗ checked 2026-09-25Sign-in combines the account's email with a personal access key, both encoded together as Basic authentication.
Source: nethunt.com ↗ checked 2026-09-25One technical entry point lists every folder the signed-in user is allowed to see.
Source: nethunt.com ↗ checked 2026-09-25A 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
NetHunt's open documentation doesn't list a daily number for how many technical requests an account can send — if a scenario turns out to be heavy, we check the real load with the vendor before relying on it.
Screenshots
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.
or write to info@coreviaflow.space
Questions
Does NetHunt replace Gmail?
No — it's built inside Gmail, so email stays where your team already works, just linked to client records.
Can WhatsApp and Instagram messages reach NetHunt?
Yes — both have a ready connection, so messages land already linked to the client.
How does NetHunt tell other tools about a change?
Through a connecting service such as Zapier, which passes the change onward automatically instead of someone exporting data by hand.
Are there published limits on daily requests?
NetHunt's documentation doesn't list a daily number — we check the real load together before connecting anything heavy.
Tell us what needs to be connected
Describe the task in text or a voice message. We look at your setup and reply with a plan.
What you can order
Four services people come to us for most often. Each page explains what we do, how the work goes and where to start.
CRM implementation
Choose the system, set up the pipeline, migrate data, train the team.
Learn more →CRM integration
Accounting, telephony, website, payments and messengers feed the CRM on their own.
Learn more →Telegram chatbots for business
Orders, requests and answers around the clock, straight into your CRM.
Learn more →n8n and Make automation
Flows between CRM, email, spreadsheets, payments and AI, on your own server.
Learn more →Pairs with NetHunt CRM
Related integrations
CRMUAKeyCRM
Ukrainian CRM that pulls orders from your site, marketplaces and chat apps into one pipeline
See scenarios →
CRMEUPipedrive
The deal-focused CRM: connect it once, and deals, contacts and follow-ups keep themselves in sync
See scenarios →
CRMUSHubSpot
US CRM with built-in calling and no-code automation, ready to plug into the tools you already run
See scenarios →
CRMUSZoho CRM
US CRM with a dedicated bulk data channel and a step-by-step process enforcer, built to plug into your existing tools
See scenarios →
IP telephonyUABinotel
IP telephony with ready-made CRM links and one-click calling
See scenarios →
CRMUASalesDrive
The CRM built for order-taking: every lead from every channel lands in one place on its own
See scenarios →Implementation · Development · Integrations →
NetHunt CRM is a trademark of its owner. CoreviaFlow is not affiliated with it unless stated otherwise. Screenshots are taken from public vendor materials; the source is shown under each one.