Integration

NetHunt CRM integration

NetHunt CRM is a CRM that lives inside Gmail and Google Workspace. List the folders (record types such as Contacts, Companies or Deals) and their fields; find records by id or text query; create, update and delete records; add comments and call logs to records; link a Gmail thread to a record; and poll a folder for records, comments, call logs and Google Drive files created, or records changed, since a given time. Authentication is HTTP Basic: the NetHunt account email address as the username and the API key (Settings > Apps and other integrations) as the password.

Connect NetHunt CRM How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in NetHunt CRM.Built from the 17 NetHunt CRM tools below, on the connection you add once.

What you can do with NetHunt CRM

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Auth test, 1 operation

verify_credentialsVerify credentialsGETChecks the connection's email and API key and returns the name and email address of the NetHunt user they belong to.

Create call log, 1 operation

create_call_logCreate call logPOSTLogs a call on a record, with its notes, the time the call started (UTC) and its duration in minutes. Returns the new call log's id.

Create comment, 1 operation

create_commentCreate commentPOSTAdds a text comment to a record and returns the new comment's id and creation time.

Create record, 1 operation

create_recordCreate recordPOSTCreates a record in one folder from a map of field names to values (list_folder_fields gives the names). Multi-value fields take arrays, link fields take record ids, country fields take ISO alpha-2 codes.

Delete record, 1 operation

delete_recordDelete recordPOSTDeletes a record. The answer is an empty object.

Find record, 1 operation

find_recordsFind recordsGETFinds records in one folder, either one record by its recordId or the records matching a text query (NetHunt search syntax, for example Name:Doe). Pass recordId or query. Returns 1 record unless limit says otherwise.

Folder field, 1 operation

list_folder_fieldsList folder fieldsGETLists the field names of one folder. These names are the keys of a record's fields object in create_record, update_record and the record listings.

Link gmail thread, 1 operation

link_gmail_threadLink gmail threadPOSTLinks a Gmail conversation to a record by its Gmail thread id, so the emails show on the record. The answer is an empty object.

New call log, 1 operation

list_new_call_logsList new call logsGETLists the call logs added to records of one folder after a given time (by default the last 24 hours), with the call's text, start time, end time and duration.

New comment, 1 operation

list_new_commentsList new commentsGETLists the comments added to records of one folder after a given time (by default the last 24 hours), with the record each belongs to.

New gdrivefile, 1 operation

list_new_google_drive_filesList new google drive filesGETLists the Google Drive files attached to records of one folder after a given time (by default the last 24 hours), with each file's name, MIME type and Drive link.

New record, 1 operation

list_new_recordsList new recordsGETLists the records created in one folder after a given time (by default the last 24 hours), with their field values.

Readable folder, 1 operation

list_readable_foldersList readable foldersGETLists every NetHunt folder (record type such as Contacts, Companies or Deals) the connected user can read, with each folder's id and name.

Record change, 1 operation

list_record_changesList record changesGETLists the change history of a folder's records after a given time (by default the last 24 hours), for one record or all of them. Each change says who made it, whether the record was created, updated or deleted, and what each field gained or lost.

Update record, 1 operation

update_recordUpdate recordPOSTUpdates a record's fields. fieldActions maps each field name to add (values to add), remove (values to remove) or overwrite (true clears the field first). A non-empty single-value field needs remove or overwrite.

Updated record, 1 operation

list_updated_recordsList updated recordsGETLists the records of one folder updated after a given time (by default the last 24 hours), with their current field values. Pass fieldName to watch only changes to some fields.

Writable folder, 1 operation

list_writable_foldersList writable foldersGETLists the NetHunt folders the connected user can create records in, with each folder's id and name; use one of these ids with create_record.

Use NetHunt CRM from Claude Code, Cursor or Codex

Connect NetHunt CRM in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its NetHunt CRM operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect NetHunt CRM

Create your workspace
Sign up free. Nothing to install.
Connect NetHunt CRM once
Add your NetHunt CRM connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.