Integration
Connect NetHunt CRM to Fergus
When something happens in NetHunt CRM, your agent does the next thing in Fergus. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want NetHunt CRM and Fergus to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What NetHunt CRM can start in Fergus
When New Call Log in NetHunt CRM
then Add Calendar Event in Fergus
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with NetHunt CRM and Fergus
Triggers and actions 8 triggers · 39 actions
- New Call Log
Triggered when a new call log is added to a record in the specified folder.
- New Comment
Triggered when a new comment is added to a record in the specified folder.
- New folder
Triggered when a new folder is added.
- New Google Drive File in Folder
Polls a NetHunt folder for newly attached Google Drive files linked to its records. Input: folder_id. Returns the list of new Google Drive file attachments.
- New or Updated Record in Folder
Triggered when a record is created or updated in the specified folder.
- New Record in Folder
Triggered when a record is created in the specified folder.
- Two-way sync new or updated records in folder
A trigger for two-way syncing new and updated records in a specified folder, with enhanced on-the-fly mapping. Can only be used with enhanced two-way sync actions that support on-the-fly mapping.
- Updated Record in Folder
Triggered when a record is updated in the specified folder.
- Add Call Log
Add a call log to the specified record.
- Add Comment
Add a comment to the specified record.
- Delete Record
Delete a record by ID.
- Find Record
Search records in a folder by ID or text query.
- Find record by field value
Finds one record in a NetHunt folder by matching a field value, and projects the record's fields map alongside record_id / id / created_at.
- List Folder Fields
List the fields of a folder.
- List Readable Folders
List all folders the user can read.
- List Writable Folders
List folders the user can create records in.
- Add Calendar Event
Creates a new calendar event/booking.
- Add Contact
Creates a new contact.
- Add Note
Creates a new note against a record.
- Add Quote
Creates a new draft quote on a Fergus job. Supported for jobs whose job type is Quote or Estimate.
- Add Task
Creates a new task in Fergus, optionally linked to a job and assigned to employees.
- Archive Site
Archives a site in Fergus. The site can later be restored.
- Create Customer
Creates a new customer.
- Create Job
Creates a job in Fergus — an active job, a draft job, or a variation of an existing job.
- Create Site
Creates a new site.
- Delete Customer
Deletes a Fergus customer by ID.
- Edit Draft Job
Updates a draft job in Fergus. Only draft jobs can be edited; leave a field blank to keep its current value.
- Finalize Draft Job
Finalises a draft job in Fergus, turning it into an active job.
- Find All Quotes
Returns up to 100 quotes from across all jobs that match the specified status and date criteria.
- Find Customer
Returns the customers whose name, or main or billing contact's name, email or phone, contains the search text.
- Find Site
Finds sites by name, city, postal code, or free-text search. Returns the first page of matches (up to 10).
- Get Calendar Event
Returns a single Fergus calendar event by its ID, including title, start/end times, event type, assigned user, linked job/job phase and recurrence details.
- Get Contact
Returns a single Fergus contact (customer or site contact) by its ID, including name, position, company and contact items.
- Get Customer by ID
Returns a Fergus customer by its ID.
- Get Customer Invoice
Retrieves a customer invoice by ID.
- Get Job by ID
Retrieves a specific job using its unique ID.
- Get Quotes for Job
Returns all quotes for a Fergus job, optionally filtered by status.
- Get Site by ID
Retrieves a specific site using its unique ID.
- List Contacts
Lists contacts, with optional filtering.
- List Customer Invoices
Lists customer invoices, with optional filtering.
- List Notes
Returns the notes (with their replies) attached to a Fergus record.
- List Tasks
Lists the company's tasks, optionally filtered by status, assigned employee, job, due date range or overdue state.
- Update Contact
Updates an existing customer contact or site contact in Fergus.
- Update Customer
Updates an existing customer's details.
- Update Quote
Updates a draft quote on a Quote or Estimate job in Fergus: title, description and its sections with line items.
- Update Site
Updates an existing site's details.
- Update Task
Updates a task's description, due date, or assigned employees in Fergus. The job a task is linked to cannot be changed.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from NetHunt CRM
NetHunt CRM to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
NetHunt CRM to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
NetHunt CRM to StripeStripe is a payment processing platform for online businesses.
NetHunt CRM to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
NetHunt CRM to PipedrivePipedrive is a sales CRM and pipeline management tool.
NetHunt CRM to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
More into Fergus
HubSpot to FergusHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to FergusGoogle Sheets
Gmail to FergusGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to FergusGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
NetHunt CRM and Fergus, answered
What can start an automation from NetHunt CRM?
Any of NetHunt CRM's 8 triggers in the catalog, including New Call Log, New Comment, New folder and New Google Drive File in Folder. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Fergus when something happens in NetHunt CRM?
Any of Fergus's 31 actions, including Create Customer, Create Job, Create Site and Update Contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Fergus to NetHunt CRM?
Fergus has no triggers in the catalog today, so automations start in NetHunt CRM. If you need the other direction, ask: your agent reads Fergus's API documentation and adds it.
Do I have to build a connector for NetHunt CRM or Fergus?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.