NetHunt CRM

Work records in NetHunt, the Gmail-native CRM: agents discover folders and their field schemas, find, create, update, and delete records, and log comments and calls to keep interaction history complete.

9 actions Basic auth available

NetHunt CRM website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

A new order lands from the storefront

List Folder Fields reads the Contacts folder schema so incoming data maps to real field names

Find Records matches the buyer by email against the folder

Create Record adds genuinely new buyers; Update Record refreshes the rest with add-mode field actions

The flow diffs incoming values against fields the team filled in by hand

Where the import conflicts with hand-entered data, the record owner chooses which version survives

Create Comment logs the order context against the record for the next person who opens it

The pipeline channel gets the day's new and updated counts

What This Integration Enables

NetHunt's bet is that the CRM should live inside Gmail, where the actual selling happens, and the price of that bet is the usual one: the record is only as good as what gets logged. FlowRunner agents take over the logging. They discover folder schemas at runtime, match inbound events to existing records, and apply updates through NetHunt's field actions, a per-field choice of add, remove, or overwrite that makes automated updates precise instead of blunt. The rep reads a complete record in their inbox; the agent did the bookkeeping. - Sync leads and customers from forms, stores, and checkout into the right folder as records - Look up and enrich contacts, companies, and deals mid-automation with Find Records - Apply per-field add, remove, and overwrite updates instead of wholesale record replacement - Log calls with notes, timing, and duration so activity history stays complete - Add comments that put workflow context where the next reader will see it - Read folder schemas first, so field mappings track the CRM as configured today

Without FlowRunner

The CRM is a second job Reps work in Gmail all day, and NetHunt records reflect whatever got copied over at week's end

Call activity evaporates Conversations happen, deals move, and the record shows none of it

Imports trample the details A bulk update flattens the carefully maintained fields under whatever the spreadsheet said

With FlowRunner

Records update from the systems where events happen Orders, forms, and inbound email keep folders current without a rep touching a field

Interaction history builds itself Calls log with notes and duration, comments capture context, and the timeline reads complete

Updates are surgical Field actions add, remove, or overwrite per field, so automation changes exactly what it means to

Use Case Scenarios

The order that files itself

A [Shopify](/integrations/shopify) order triggers the flow. Find Records checks the Contacts folder for the buyer's email; new buyers get Create Record with fields shaped by List Folder Fields, and returning buyers get Update Record adding the purchase to their history without disturbing anything else. Create Comment drops the order summary on the record, so when the customer replies to their confirmation email, the rep reading it in Gmail sees the whole picture beside the thread.

Inbound email becomes logged pipeline activity

When a prospect writes in through [Gmail](/integrations/gmail-service), the flow matches the sender with Find Records and logs the exchange with Create Comment against their record. Calls made through the team's phone system land as Log Call entries with notes and duration attached to the right contact. The Friday pipeline review stops with the question "what happened with this account", because the record already answers it.

The pipeline report without the export

On a schedule, Find Records pulls the Deals folder with a field query for open stages, and the flow writes the snapshot to [Google Sheets](/integrations/google-sheets) with owner, value, and age per deal. Deals with no logged activity in two weeks get flagged to [Slack](/integrations/slack) with a link back to the record. List Readable Folders and List Writable Folders run as preflight, so a permissions change surfaces as an alert, not as a mysteriously empty report.

Human-in-Loop Highlight

The destructive write in NetHunt is not just Delete Record; it is Update Record with Overwrite enabled. Field actions default to surgical changes, but overwrite mode replaces a field's existing values with the incoming ones, and in a bulk enrichment run that means the phone number a rep confirmed on a call last Tuesday gets replaced by whatever a data vendor's CSV believes. The overwritten value does not come back. So FlowRunner enrichment flows draw the line by field state: writes into empty fields flow freely, but any run that would overwrite populated fields stops and posts the diff, record by record, current value against incoming value. The record owner keeps the confirmed direct line, accepts the corrected company name, and approves the rest. Delete Record sits behind the same discipline, executed only against a person-confirmed ID. Enrichment at machine speed, but no agent silently discards data a human took the trouble to get right.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

9 actions

Folders and Schema

List Readable Folders Lists the folders, NetHunt's CRM objects such as Contacts, Companies, and Deals, that the account can read, with IDs for record lookups and schema reads.
List Writable Folders Lists the folders where the account can create records. The preflight that catches permission gaps before a write fails mid-flow.
List Folder Fields Returns a folder's field schema, names and types, so record payloads map to the CRM as configured today rather than as remembered.

Records

Find Records Searches a folder by direct record ID or a text query using NetHunt's advanced search syntax, including field-scoped matches. Returns records with IDs, timestamps, and field values. The matching step behind every sync on this page.
Create Record Creates a record in a folder from a fields object keyed to the folder's schema, returning the new ID and stored values.
Update Record Updates a record through per-field actions that add, remove, or overwrite values, with overwrite as an explicit choice. The precision instrument this page's human gate keeps pointed the right way.
Delete Record Permanently deletes a record by ID. Cannot be undone, so it runs only against IDs a person has confirmed.

Activity

Create Comment Adds a text comment to a record, putting workflow context, order summaries, and email exchanges where the next reader will find them.
Log Call Logs a phone call against a record with notes, occurrence time, and duration in seconds. The step that keeps interaction history complete without a rep typing it.

Frequently Asked Questions

What can FlowRunner do with NetHunt CRM?

FlowRunner agents can run List Readable Folders, List Writable Folders, and List Folder Fields in NetHunt CRM, plus 6 more actions.

Does connecting NetHunt CRM to FlowRunner require OAuth?

No. NetHunt CRM connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can NetHunt CRM trigger a FlowRunner workflow automatically?

NetHunt CRM doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with NetHunt CRM

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us