Integration
Connect NetHunt CRM to ITIS
When something happens in NetHunt CRM, your agent does the next thing in ITIS. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want NetHunt CRM and ITIS 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 CodeEverything your agent can do with NetHunt CRM and ITIS
Triggers and actions 8 triggers · 21 actions
Trigger
New Call LogTriggered 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. 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.
- 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.
Action
Convert LSID to TSNGet the TSN for a given LSID (Life Science Identifier).
- Convert TSN to LSID
Get the LSID (Life Science Identifier) for a given TSN.
- Find taxon by common name
Search ITIS for taxa matching a common (vernacular) name.
- Find taxon by scientific name
Search ITIS for taxa matching a scientific name.
- Find taxon by search term
Search ITIS across scientific and common names for any matching term.
- Get accepted names
Get the currently accepted scientific name(s) for a given TSN, when the queried TSN is not itself accepted.
- Get common names
Get the common (vernacular) names associated with a given TSN.
- Get full hierarchy
Get the complete taxonomic hierarchy (ancestors and descendants) for a given TSN.
- Get full record
Get the complete taxonomic record for a given TSN (taxonomic serial number).
- Get hierarchy down
Get the taxonomic hierarchy below (children of) a given TSN.
- Get hierarchy up
Get the taxonomic hierarchy above (ancestors of) a given TSN.
- Get parent taxon
Get the parent TSN for a given TSN.
- Get synonym names
Get the synonym scientific names associated with a given TSN.
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