Connect Ontraport to NetHunt CRM

Both apps 35Ontraport 19NetHunt CRM 16

• Trigger
  New Contact

  Polling trigger: fires for each newly created contact, newest first (sorted by creation date).

• Trigger
  New or Updated Contact

  Polling trigger: fires when a contact is created or modified, sorted by date last modified.

• Trigger
  New Task

  Polling trigger: fires for each newly created task (objectID 1), newest first.

• Trigger
  New Transaction

  Polling trigger: fires for each newly created transaction (objectID 46), newest first.

• Trigger
  Two-way sync new or updated contact

  A trigger for two-way syncing new and updated contacts, with enhanced on-the-fly mapping. Polls Ontraport Contacts sorted by date-last-modified descending; fires for each new or updated contact.

• Action
  Create Object

  Create a record of any Ontraport object type. Provide objectID and a JSON of fields. Note: Ontraport DROP (dropdown) custom fields fail OPEN — sending a value that is not one of the field's defined options returns HTTP 200 and silently discards it, leaving the field unset. Verify a dropdown value landed by reading the record back.

• Action
  Create or Update Contact

  Create a new contact, or merge into an existing one matched by email (Ontraport saveorupdate). Note: Ontraport DROP (dropdown) custom fields fail OPEN — sending a value that is not one of the field's defined options returns HTTP 200 and silently discards it, leaving the prior value in place. Verify a dropdown value landed by reading the record back.

• Action
  Create Task

  Create a Task object (objectID 1) in Ontraport.

• Action
  Delete Contact

  Delete a contact by its Ontraport ID.

• Action
  Delete Object

  Delete a record of any object type by objectID and id.

• Action
  Find Contact by Email

  Find a contact by exact email match. Returns the first matching record.

• Action
  Find contact by field (Go only has Find Contact by Email — covers email lookup only, not arbitrary field)

  Returns the details for a contact if the specified field matches the specified value. Throws an error if zero or multiple match.

• Action
  Get Contact

  Retrieve a single contact by its Ontraport ID.

• Action
  Get Object

  Retrieve a single record of any object type by objectID and id.

• Action
  List Contacts

  List contacts with optional search, range, and sort.

• Action
  List Objects

  List records of any object type with optional search and range.

• Action
  Remove Tag from Contact

  Remove a tag from one or more contacts.

• Action
  Tag Contact

  Add a tag to one or more contacts.

• Action
  Update Object

  Update a record of any Ontraport object type by ID. Note: Ontraport DROP (dropdown) custom fields fail OPEN — sending a value that is not one of the field's defined options returns HTTP 200 and silently discards it, leaving the prior value in place. Verify a dropdown value landed by reading the record back.

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

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.