Integration

Connect NetHunt CRM and Particle

When New Record in Folder fires in NetHunt CRM, your agent runs Publish an event in Particle, or New device event (instant) in Particle to Find Record in NetHunt CRM. 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 Particle to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Examples

Pick one to fill the box, then change anything: the steps, the wording, even the apps. Go as long as you like.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

One 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.ai

Start 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)

NetHunt CRM holds the customer and device records your team works from in Gmail, while Particle carries what the hardware in the field is reporting. Connecting them lets device events write back to the right NetHunt record, and lets changes in a NetHunt folder publish events or update ledger data in Particle.

Example flows

What NetHunt CRM and Particle can do together

From NetHunt CRM to Particle

From Particle to NetHunt CRM

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 Particle

Triggers and actions 9 triggers · 13 actions

Each app on its own

Reviews

What our customers say

More from NetHunt CRM

More into Particle

Questions

NetHunt CRM and Particle, answered

How does a Particle event find the right record in NetHunt CRM?

The agent uses Find record by field value to match a field such as the device serial carried on the event, or Find Record to search a folder by text query. If no record matches, nothing is written, and the agent tests every scenario before it runs.

Can a change in NetHunt CRM reach a device?

Yes. A new or updated record in a NetHunt folder can publish an event to the device cloud in Particle, or set ledger instance data that devices read, and the agent can also run a configured Logic function and list devices when it needs fleet details.

What can start an automation from NetHunt CRM?

Any of NetHunt CRM's 8 triggers in the catalog, including New Record in Folder, Updated Record in Folder, New Call Log and New Comment. Describe the moment in plain language and your agent picks the right one.

What can your agent do in Particle when something happens in NetHunt CRM?

Any of Particle's 5 actions, including Publish an event, Set ledger instance data, Execute a logic function and Get ledger instance. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from Particle to NetHunt CRM?

Yes. When something happens in Particle, your agent can act in NetHunt CRM too. This page covers both directions: Particle's triggers and NetHunt CRM's actions are listed here as well.

Do I have to build a connector for NetHunt CRM or Particle?

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 Particle 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.