Connect MOCO to NetHunt CRM

Both apps 66MOCO 50NetHunt CRM 16

• Trigger
  New Client

  Triggers when a new client is created.

• Trigger
  New Company

  Triggers when a new company is created.

• Trigger
  New Expense

  Triggers when an expense is created.

• Trigger
  New Exported Invoice (Bookkeeping)

  Triggers when a new invoice is exported (for the bookkeeping).

• Trigger
  New Incoming Payment

  Triggers when a new incoming payment is created.

• Trigger
  New Invoice

  Triggers when a new invoice is created.

• Trigger
  New Invoice Status

  Triggers when the status of an invoice is changed.

• Trigger
  New Offer

  Triggers when a new offer is created.

• Trigger
  New Outgoing Payment

  Triggers when a new outgoing payment is created.

• Trigger
  New Planning Entry

  Triggers when a new Planning Entry is created.

• Trigger
  New Presence

  Triggers when a new Presence is created.

• Trigger
  New Project Assignment

  Triggers when a person is assigned to a project.

• Trigger
  New Purchase

  Triggers when a new purchase is created.

• Trigger
  New Recurred Expense

  Triggers when an expense is recurred.

• Trigger
  New Task

  Triggers when a new task is created.

• Trigger
  New Time Entry

  Triggers when a new time entry is created.

• Trigger
  Unarchived Project

  Triggers when a project is made active again.

• Trigger
  Updated Company

  Triggers when a company was updated.

• Trigger
  Updated Expense

  Triggers when an expense was updated.

• Trigger
  Updated Invoice

  Triggers when an invoice was updated.

• Trigger
  Updated Lead

  Triggers when a lead was updated.

• Trigger
  Updated Planning Entry

  Triggers when a Planning Entry was updated.

• Trigger
  Updated Presence

  Triggers when a Presence was updated.

• Trigger
  Updated Project

  Triggers when a project was updated.

• Trigger
  Updated Purchase

  Triggers when a purchase was updated.

• Trigger
  Updated Time Entry

  Triggers when a time entry was updated.

• Action
  Create Comment

  Creates a new Comment.

• Action
  Create Company

  Creates a new company (customer only).

• Action
  Create Contact

  Creates a new contact person.

• Action
  Create Expense

  Creates a new Expense.

• Action
  Create Incoming Payment

  Creates a new incoming payment.

• Action
  Create Lead

  Creates a new lead.

• Action
  Create Outgoing Payment

  Creates a new outgoing payment.

• Action
  Create Project

  Creates a new Project.

• Action
  Create Purchase

  Creates a new Purchase.

• Action
  Create Task

  Creates a new project task.

• Action
  Create Time Entry

  Create a new time entry.

• Action
  Find Company

  Finds an existing Company.

• Action
  Find Contact

  Finds an existing Contact.

• Action
  Find Expense

  Finds an existing Expense.

• Action
  Find Invoice

  Finds an existing Invoice.

• Action
  Find Lead

  Finds an existing lead.

• Action
  Find Offer

  Finds an existing Offer.

• Action
  Find Planning Entry

  Finds an existing Planning Entry.

• Action
  Find Project

  Finds an existing project.

• Action
  Find Purchase

  Finds an existing Purchase.

• Action
  Find Task

  Finds an active Task for a Project.

• Action
  Find Time Entry

  Finds an existing Time Entry.

• Action
  Find User

  Finds an existing active user.

• Action
  Record Presence

  Record a new presence.

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