NetHunt CRM
NetHunt is a Gmail CRM that brings sales automation and drip campaigns straight to your inbox
Verdict
Common use cases
- Pull contact history before a sales call
- Track which deals updated this week
- Find call logs from a specific account
- Check recent comments on support tickets
- Locate Google Drive files linked to a deal
Integration
- Vendor
- NetHunt CRM
- Category
- crm
- Auth
- OAUTH2
- Tools
- 12
- Composio slug
nethunt_crm
Tools
- Delete Recorddestructive
Tool to delete a NetHunt CRM record by ID. Use when you need to permanently remove a record from the system.
- Find Records
Tool to find records by ID or text query in NetHunt CRM. Search for records within a folder using record ID or search query. Use when you need to locate specific records in a folder.
- Get New Call Logs
Find recently created call logs in NetHunt CRM. Returns call logs created after a specified time. Use when you need to retrieve new call activity from a specific folder.
- Get New Comments
Tool to find recently created record comments in a NetHunt CRM folder. Returns comments created after a specified time (defaults to last 24 hours).
- Get New Google Drive Files
Tool to find recently created Google Drive files linked to NetHunt CRM records. Use when you need to retrieve files created after a specific time in a NetHunt folder. Returns file metadata including Google Drive links, MIME types, and assoc
- Get New Records
Tool to find recently created records in NetHunt CRM. Use when you need to retrieve records that were created after a specific time in a given folder. Returns record details including ID, creation time, and field values. If no 'since' time
- Get Record Changes
Tool to find recent record changes in a NetHunt CRM folder. Returns change history including CREATE, UPDATE, DELETE actions with field-level diffs. Use when you need to track modifications to records, audit changes, or sync data based on re
- Get Updated Records
Tool to find recently updated records in NetHunt CRM. Returns records updated after a specified time, optionally filtered by field names. Use when you need to track changes or sync records that have been modified.
- List Folder Fields
Tool to list folder fields in NetHunt CRM. Returns the field definitions for a specific folder. Use when you need to retrieve all field metadata for a given folder ID.
- List Readable Folders
Tool to list all accessible folders in NetHunt CRM. Returns folders the user has read access to. Use when you need to retrieve available folders for organizing or accessing records.
- List Writable Folders
Tool to list folders the user can create records in. Returns folders the user has write access to. Use when you need to retrieve writable folders for creating new records.
- Test NetHunt CRM Authentication
Tool to verify request credentials and test authentication. Returns information about the authenticated user including name and email. Use this action to confirm API credentials are valid before making other requests.
Setup
Setup guide
- 11. In Switchy, open Settings and navigate to the Integrations page. 2. Find NetHunt CRM in the MCP directory and click Connect. 3. You'll be redirected to NetHunt's OAuth consent screen — sign in with the Google account that has NetHunt installed. 4. Grant Switchy read and write access to your NetHunt records, comments, and linked Google Drive files (the scopes cover viewing, creating, updating, and deleting records). 5. After authorizing, you'll return to Switchy and see NetHunt CRM listed as connected. 6. Open any Space and type '@NetHunt find records in folder [your-folder-id] matching [search term]' to test — replace the placeholders with a real folder ID from your NetHunt workspace and a contact name or company. 7. If the MCP returns matching records, the connection works and you can start querying your CRM data in conversations.
What teammates see: by default, memories from NetHunt CRM are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Recent Pipeline Changes
@NetHunt get updated records from folder [folder-id] since 48 hours ago. Show me which fields changed and the current stage for each deal.Open in a Space →
New Lead Activity
@NetHunt get new records from folder [folder-id] created in the last 24 hours. Include contact name, company, and source.Open in a Space →
Call Log Summary
@NetHunt get new call logs from folder [folder-id] since yesterday. Summarize the key points from each call.Open in a Space →
Find Contact by Name
@NetHunt find records in folder [folder-id] matching 'Acme Corp'. Show me the contact info and any recent comments.Open in a Space →
Attached Files Check
@NetHunt get new Google Drive files from folder [folder-id] created in the last 7 days. List the file names and which records they're attached to.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@nethunt find all records in our Sales Pipeline folder where the company name contains 'Acme' and show me their current deal stage
Found 3 records matching 'Acme' in your Sales Pipeline folder: Acme Corp (Deal Stage: Proposal Sent, Value: $45K, Last Contact: 2 days ago), Acme Industries (Deal Stage: Negotiation, Value: $78K, Last Contact: 5 hours ago), and Acme Solutions (Deal Stage: Qualified Lead, Value: $12K, Last Contact: 1 week ago). All records include contact details and recent activity timestamps. This illustrative example shows how text search returns structured CRM data with custom field values.
Requires OAuth2 connection with read access to the specified folder. Search behavior depends on your NetHunt folder schema — custom fields like 'Deal Stage' must exist in your setup. Results are limited by NetHunt's API pagination (typically 100 records per call), so large result sets may require follow-up queries.
@nethunt create a new record in our Leads folder for Sarah Chen at TechVentures Inc, email sarah.chen@techventures.io, and set the lead source to 'Conference - CloudExpo 2024'
Created new record in Leads folder: Sarah Chen (ID: rec_8x9k2m). Record includes email sarah.chen@techventures.io, company TechVentures Inc, and lead source Conference - CloudExpo 2024. The record is now visible in your NetHunt CRM and will appear in folder views and reports. This example demonstrates how the MCP handles record creation with multiple field assignments in a single operation.
Requires OAuth2 write permissions to the target folder. Field names like 'lead source' must match your folder's custom field schema exactly (case-sensitive). Side-effect: this immediately creates a permanent record — there's no draft mode. If your team has automation rules triggered on record creation, those will fire immediately.
@nethunt get all records updated in the last 48 hours in our Customer Success folder, then summarize which accounts had status changes and what the new statuses are
Retrieved 17 updated records from Customer Success folder. Status changes identified: 5 accounts moved to 'At Risk' (including MegaCorp due to support ticket volume), 3 upgraded to 'Champion' status (DataFlow Inc now has 3 active advocates), 2 downgraded to 'Churned', and 7 had contact detail updates without status changes. Most status changes occurred yesterday between 2-4pm, suggesting a team review session. This synthesis combines the MCP's change-tracking with AI analysis to surface patterns.
Combines Get Updated Records tool with AI reasoning to identify meaningful patterns. The 48-hour window is configurable but longer periods may hit rate limits on large folders. Change detection relies on NetHunt's update timestamps — bulk imports or API updates from other tools will appear as 'updates' even if data is unchanged.
Use-case deep-dives
When NetHunt wins for client onboarding between sales and delivery
An 8-person agency closes a new client in NetHunt, and the account manager needs the full context before kickoff. Use Get Record Changes to pull the entire deal history—emails, call logs, proposal revisions—into a single AI summary. The MCP surfaces who said what and when, so the AM walks into the first call knowing the client's objections and promises made. This works because NetHunt lives in Gmail; the change log captures every touchpoint without manual data entry. If your sales cycle is under 30 days and your team uses Google Workspace, this MCP turns CRM archaeology into a 90-second brief. Skip it if you're on Salesforce or your deals span six months—the tooling won't justify the OAuth setup for infrequent lookups.
When this MCP replaces your Friday deal-status Slack thread
A 4-person SaaS startup runs a weekly pipeline review where the founder asks 'what moved this week?' Get Updated Records pulls every deal that changed since last Friday, filtered by stage or owner. The AI reads the diffs, flags stalled opportunities, and drafts follow-up tasks without opening the CRM. This scenario wins when your pipeline is under 100 active deals and you're not running complex multi-stage workflows. NetHunt's folder structure maps cleanly to sales stages, so the MCP can answer 'show me deals stuck in demo for over two weeks' in one query. If your pipeline exceeds 200 deals or you need forecasting logic, you'll hit the 12-tool ceiling fast—consider a heavier CRM integration instead.
When NetHunt bridges your helpdesk and customer history for support teams
A 6-person support team gets a ticket from a customer who's been quiet for three months. Use Find Records to pull their NetHunt profile, then Get New Comments and Get New Call Logs to see the last five interactions across sales and success. The AI summarizes contract status, known issues, and the last promise made, so the support rep replies with full context in under two minutes. This works when your support volume is under 50 tickets a day and your CRM is the source of truth for customer relationships. NetHunt's Gmail integration means every email is already logged, so the MCP doesn't rely on manual note-taking. If your support team is over 10 people or you're fielding 100+ daily tickets, the OAuth latency and 12-tool limit will bottleneck triage speed.
Frequently asked
What does the NetHunt CRM MCP do in Switchy?
It connects your NetHunt CRM workspace so AI agents can search records, track changes, pull call logs, and manage Google Drive files linked to deals or contacts. Agents can find records by ID or text query, monitor new comments, and see field-level edit history. You can also delete records programmatically, though that requires explicit confirmation in most workflows.
Do I need admin access to connect NetHunt CRM?
NetHunt uses OAuth2, so you'll authenticate with your NetHunt account credentials. You don't strictly need admin rights, but the connection inherits your user permissions—if you can't see a folder or delete records in NetHunt's UI, the MCP can't either. Most teams have the account owner or a CRM manager connect it to avoid scope gaps.
Can the MCP create or update NetHunt records?
No. The current tool set is read-heavy: you can find records, pull change logs, and delete records, but there's no "Create Record" or "Update Record" tool. If you need to write data back into NetHunt, you'll have to use NetHunt's native API or Zapier. The MCP is built for reporting, auditing, and syncing data out, not for data entry.
How is this different from using NetHunt's API directly?
The MCP wraps NetHunt's API in natural-language tools, so you can ask "show me deals updated in the last week" instead of writing GET requests with timestamp filters. It's faster for ad-hoc queries and reporting. If you're building a custom integration or need bulk writes, the raw API gives you more control—but you'll write more code.
Who on the team should connect this MCP?
Whoever owns your NetHunt workspace or has visibility into all the folders your team cares about. Sales ops or the CRM admin are common choices. Avoid connecting it with a rep's personal account—if they leave, the connection breaks. The MCP doesn't consume NetHunt seats, but it does count as one connected integration in your Switchy plan.