Connect NetHunt CRM to Moxie

Both apps 61NetHunt CRM 16Moxie 45

• 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
  Agreement Sent

  Triggers when a proposal is sent either via link or email.

• Trigger
  Agreement Signed

  Triggers when an agreement is accepted and signed with e-signature.

• Trigger
  Agreement Viewed

  Triggers when a user views the proposal.

• Trigger
  Client Created

  Triggers when a new client is created in Moxie.

• Trigger
  Client Deleted

  Triggers when a client record is deleted in Moxie.

• Trigger
  Client Updated

  Triggers when a client record is updated in Moxie.

• Trigger
  Form Completed

  Triggers when a form is completed.

• Trigger
  Invoice Sent

  Triggers when an invoice is sent in Moxie.

• Trigger
  Meeting Cancelled

  Triggers when a meeting is cancelled

• Trigger
  Meeting Scheduled

  Triggers when a new meeting is scheduled

• Trigger
  Meeting Updated

  Triggers when a meeting is updated or rescheduled

• Trigger
  Opportunity Created

  Triggered with a pipeline opportunity is created

• Trigger
  Opportunity Deleted

  Triggered with a pipeline opportunity is deleted

• Trigger
  Opportunity Updated

  Triggered with a pipeline opportunity is updated

• Trigger
  Payment Received

  Triggers when a payment is received either vial Stripe or manual entry.

• Trigger
  Project Completed

  Triggers when a project is set to "complete" in Moxie.

• Trigger
  Project Created

  Triggers when a new project is created in Moxie.

• Trigger
  Project Updated

  Triggers when the settings for a project are updated.

• Trigger
  Proposal Sent

  [DEPRECATED - Please use "Agreement Sent"] - Triggers when a proposal is sent either via link or email.

• Trigger
  Proposal Signed

  [DEPRECATED - Please use "Agreement Signed"] - Triggers when a proposal is accepted and signed with e-signature.

• Trigger
  Proposal Viewed

  [DEPRECATED - Please use "Agreement Viewed"] - Triggers when a user views the proposal.

• Trigger
  Task Approval

  Triggers when a new Deliverable is ready for client approval.

• Trigger
  Task Created

  Triggered when a Project Task is created

• Trigger
  Task Deleted

  Triggered when a Project Task is deleted

• Trigger
  Task Updated

  Triggered with a Project Task is updated.

• Trigger
  Ticket Closed

  Triggers and a support ticket is closed

• Trigger
  Ticket Comment

  Triggers when a comment is created on a ticket

• Trigger
  Ticket Created

  Triggers when a new support ticket is created

• Trigger
  Ticket Deleted

  Triggers when a support ticket is deleted

• Trigger
  Ticket Updated

  Triggers when a support ticket is updated

• Trigger
  Time Worked Created

  Triggers when a new time worked entry is created.

• Trigger
  Time Worked Deleted

  Triggers when a time worked record is deleted.

• Trigger
  Time Worked Updated

  Triggers when a time worked entry has been updated.

• Action
  Create Client

  Creates a new client record in Hectic

• Action
  Create Expense

  Records a new expense in your Moxie accounting records, optionally filed under a vendor and allocated to a client.

• Action
  Create Opportunity

  Create a new pipeline opportunity

• Action
  Create & Optionally Send Invoice

  Creates an invoice for a client from the line items you supply, and emails it straight away when you fill in who to send it to. Left blank, the invoice is saved as a draft.

• Action
  Create or Update Calendar Event

  Create or update a calendar event in Moxie

• Action
  Create Project

  Create a project and optionally use a template

• Action
  Create Task

  Create a task in the project management system

• Action
  Create Ticket

  Create a Ticket for a client and contact

• Action
  Create Ticket Comment

  Adds a comment (public or private) to an existing ticket.

• Action
  Create Time Worked

  Creates a time worked entry

• Action
  Delete Calendar Event

  Deletes a calendar event in Moxie by the external ID.

• Action
  Find a Client

  Finds a client by either name or contact email address.

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