Integration

Connect Intercom to NetHunt CRM

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

Intercom8 triggersIntercom30 actionsNetHunt CRM8 triggersNetHunt CRM8 actions

Browse all apps

Build it

What do you want Intercom and NetHunt CRM 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 Intercom and NetHunt CRM

Triggers and actions 16 triggers · 38 actions

Trigger
New company
Fires when a new company is created. Poll GET /companies ordered by created_at.
Trigger
New conversation
Polls for conversations, most recently updated first. Fires for each new conversation.
Trigger
New lead
Instant trigger: fires when a new lead is created in Intercom (webhook). Stub ported from dev.apiant — not yet implemented.
Trigger
New note on conversation
Instant trigger: fires when a note is added to an Intercom conversation (webhook). Stub ported from dev.apiant — not yet implemented.
Trigger
New or updated contact
Polls for contacts, most recently updated first. Fires for each new or updated contact.
Trigger
New tag on a conversation
Instant trigger: fires when a tag is added to an Intercom conversation (webhook). Stub ported from dev.apiant — not yet implemented.
Trigger
New tag on a user
Instant trigger: fires when a tag is added to an Intercom user (webhook). Stub ported from dev.apiant — not yet implemented.
Trigger
New ticket
Fires when a new ticket is created. Poll GET /tickets/search or /tickets ordered by created_at.
Action
Add company
Create (or upsert) a company in Intercom. POST /companies.
Action
Add note to contact
Adds a note to the specified contact as the specified admin.
Action
Add note to conversation
Adds an internal note to the specified conversation as an admin.
Action
Add tag to contact
Attaches a tag to the specified contact.
Action
Add ticket
Create a support ticket. POST /tickets.
Action
Assign conversation
Assigns the conversation to an admin or team.
Action
Close conversation
Closes the specified conversation.
Action
Create contact
Creates a new contact (role user or lead) in Intercom.
Action
Create message
Creates an admin-initiated email or in-app message to a contact.
Action
Delete company
Delete a company by ID. DELETE /companies/{company_id}.
Action
Delete contact
Deletes a contact by ID.
Action
Find admin by email
Fetches an admin's details. Lists all admins; match by email.
Action
Find contact by email
Searches contacts by email and returns matches.
Action
Find tickets
Search tickets by criteria. POST /tickets/search.
Action
Get company
Retrieve a company by ID. GET /companies/{company_id}.
Action
Get contact
Fetches a contact's details by ID.
Action
Get conversation
Fetches a conversation's details by ID.
Action
Get ticket
Retrieve a ticket by ID. GET /tickets/{ticket_id}.
Action
List companies
List all companies. GET /companies.
Action
List segments
List all segments. GET /segments.
Action
List tags
Lists all tags for the workspace.
Action
Open conversation
Opens (marks open) the specified conversation.
Action
Remove tag from contact
Detaches a tag from the specified contact.
Action
Send conversation reply
Sends a reply to the specified conversation as an admin.
Action
Snooze conversation
Snoozes the specified conversation until the given unix timestamp.
Action
Start conversation
Starts a new conversation with the specified contact.
Action
Track event
Submit a data event for a contact. POST /events.
Action
Update company
Update an existing company. PUT /companies/{company_id}.
Action
Update contact
Updates an existing contact specified by ID.
Action
Update ticket
Update an existing ticket. PUT /tickets/{ticket_id}.
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.

Each app on its own

The other way round: NetHunt CRM to Intercom