Integration
Connect NetHunt CRM to Npm Registry
When New Call Log fires in NetHunt CRM, your agent runs Find packages by text in Npm Registry. Describe the whole flow 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 Npm Registry to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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 Npm Registry
When New Call Log in NetHunt CRM
then Find packages by text in Npm Registry
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 Npm Registry
Triggers and actions 8 triggers · 11 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.
- Find packages by text
Searches the public npm registry for packages matching your text and returns the matching packages with their scores, ranked by relevance.
- Get package
Returns the full registry metadata for an npm package, including its description, dist-tags, every published version, publish times, maintainers and README.
- Get package version
Returns the published metadata for one version of an npm package, including its dependencies, license, maintainers and download tarball details.
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 QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
NetHunt CRM to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Npm Registry
HubSpot to Npm RegistryHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to Npm RegistryGoogle Sheets
Gmail to Npm RegistryGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Npm RegistryGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
NetHunt CRM and Npm Registry, 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 Npm Registry when something happens in NetHunt CRM?
Any of Npm Registry's 3 actions, including Find packages by text, Get package and Get package version. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Npm Registry to NetHunt CRM?
Npm Registry has no triggers in the catalog today, so automations start in NetHunt CRM. If you need the other direction, ask: your agent reads Npm Registry's API documentation and adds it.
Do I have to build a connector for NetHunt CRM or Npm Registry?
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.
Can my AI client use NetHunt CRM and Npm Registry without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.