Integration

Connect NetHunt CRM to 2Chat

When something happens in NetHunt CRM, your agent does the next thing in 2Chat. Describe it in plain language and the automation is built, tested on every branch and kept running.

NetHunt CRM8 triggersNetHunt CRM8 actions2Chat13 triggers2Chat1 action

Browse all apps

Build it

What do you want NetHunt CRM and 2Chat to do together?

Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.

Ask the assistant

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

Or work from Claude Code

Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.

Connect Claude Code

Everything your agent can do with NetHunt CRM and 2Chat

Triggers and actions 21 triggers · 9 actions

Trigger
New Call Log
Triggered when a new call log is added to a record in the specified folder.
Trigger
New Comment
Triggered when a new comment is added to a record in the specified folder.
Trigger
New folder
Triggered when a new folder is added.
Trigger
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.
Trigger
New or Updated Record in Folder
Triggered when a record is created or updated in the specified folder.
Trigger
New Record in Folder
Triggered when a record is created in the specified folder.
Trigger
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.
Trigger
Updated Record in Folder
Triggered when a record is updated in the specified folder.
Action
Add Call Log
Add a call log to the specified record.
Action
Add Comment
Add a comment to the specified record.
Action
Delete Record
Delete a record by ID.
Action
Find Record
Search records in a folder by ID or text query.
Action
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. DYNAMIC OUTPUT — DOCUMENTED EXCEPTION TO THE DESIGN RULE (2026-07-20). The standing rule puts FIND ops in the IDs-only bucket: GET enriches output with a field picker, FIND/LIST return IDs only. This op is a deliberate exception because NetHunt exposes NO get-by-id endpoint, so there is no GET op that could carry the picker. Re-confirmed against live data: ?query=<recordId> returns [] for a record that demonstrably exists in that folder (record 6a48901d931c9b3a9bbfb83c in Contacts), recordId:x 400s, and find-record-by-id 404s. The choice was therefore FIND-or-nothing, and a NetHunt user with no output picker has no way to map folder fields at all. If NetHunt ever ships a get-by-id endpoint, move the picker to a proper GET op and revert this op to IDs-only. Field values are projected under `fields`, a flat object keyed by field NAME, matching the house convention of a dynamic map beside the record's own top-level keys (cf. Agile/Cliniko/Capsule/MINDBODY `custom_fields`). NetHunt has no standard-vs-custom split — every folder field is user-defined — so the whole `fields` object is the dynamic surface and the container keeps the accurate name `fields` rather than `custom_fields`. The picker is parameterized per folder: `folder_id` is a SETTING (not an input) because dynamic-schema resolution binds only against step settings, so an input-sourced folder could never resolve the discovery at automation-load time. TYPE BLINDNESS (inherent, not fixable here): the backing schema endpoint returns only {name} with no type, so the picker advertises every field as String. Live reads return numbers and lists — e.g. Deal amount 100000 and Probability 0.9 are numbers, and Company / Contact person / Manager / Email / Label are ARRAYS (link fields carry record-id arrays). Mapping one of these as a scalar fails at runtime with no design-time signal.
Action
List Folder Fields
List the fields of a folder.
Action
List Readable Folders
List all folders the user can read.
Action
List Writable Folders
List folders the user can create records in.
Trigger
Call Status Update
Triggers when a call changes state. E.g.: ringing, missed, answered, canceled, completed, etc.
Trigger
Incoming Call Completed
Triggers when an incoming phone call is completed (answered or missed).
Trigger
New WhatsApp Conversation
Triggers when a new WhatsApp conversation is started on your 2Chat connected number.
Trigger
New WhatsApp Message
Triggers when a new message is either sent or received on 2Chat. Works for messages sent by agents or sent by your users/customers.
Trigger
Outgoing Call Completed
Triggers when an outgoing phone call is completed (answered or canceled).
Trigger
Participant Joined a WhatsApp Group
Triggers when someone joins a WhatsApp Group
Trigger
Participant Left a WhatsApp Group
Triggers when someone leaves a WhatsApp Group
Trigger
Participant Was Removed From a WhatsApp Group
Triggers when someone is removed from a WhatsApp Group
Trigger
WhatsApp Audio Message Transcribed
Triggers when a new WhatsApp audio message is transcribed to text.
Trigger
WhatsApp Call Made
Triggers when a new WhatsApp call is made from your connected number.
Trigger
WhatsApp Call Received
Triggers when a new WhatsApp call is received on your connected number.
Trigger
WhatsApp Group Message Received
Triggers when a new WhatsApp Group Message is received
Trigger
WhatsApp Order Received
Triggers when a WhatsApp Order is received on your 2Chat connected number.
Action
Create Contact
Creates a Contact in 2Chat

Each app on its own

The other way round: 2Chat to NetHunt CRM