Connect NetHunt CRM to Order Desk

Both apps 34NetHunt CRM 16Order Desk 18

• 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
  New Order Added

  Triggered when a new order is added in Order Desk.

• Trigger
  Order Folder Changed

  Triggered when an order moves to a different folder in Order Desk.

• Action
  Add Order Item

  Adds a line item to an existing order in Order Desk.

• Action
  Add Order Note

  Adds a note to an order's history in Order Desk.

• Action
  Add Shipment

  Records a shipment with tracking details against an order in Order Desk.

• Action
  Change Folder

  Moves an order into a different folder in Order Desk.

• Action
  Change Tag

  Sets the tag on an order in Order Desk. Reads the order first and writes it back with the new tag so no other order details are lost.

• Action
  Create Inventory Item

  Creates a product in the Order Desk store's inventory.

• Action
  Create New Order

  Creates a new order in Order Desk with its line items, addresses and totals.

• Action
  Delete Inventory Item

  Deletes a product from the Order Desk store's inventory.

• Action
  Delete Order

  Deletes an order from Order Desk.

• Action
  Delete Order Item

  Removes a line item from an order in Order Desk.

• Action
  Get Inventory Item

  Returns one product from the Order Desk store's inventory, including its stock level and your own metadata.

• Action
  Get Order

  Returns one order from Order Desk with its line items, addresses, shipments, notes and your own metadata.

• Action
  List Orders

  Returns orders from Order Desk, with optional folder, source, customer and date filters.

• Action
  Set Order Data

  Updates fields on an existing Order Desk order. Reads the order first and writes it back with only the fields you filled in, so nothing else is lost.

• Action
  Set Order Item Data

  Updates a line item on an Order Desk order. Reads the item first and writes it back with only the fields you filled in, so nothing else on the item is lost.

• Action
  Update Inventory Item

  Updates a product in the Order Desk store's inventory. Reads the item first and writes it back with only the fields you filled in, so nothing else is lost.

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