Connect monday.com to NetHunt CRM

Both apps 53monday.com 37NetHunt CRM 16

• Trigger
  Any Column Value Changed in Board

  Triggers when any column's value is changed in the selected board.

• Trigger
  Item Moved to Group (Same or Different Board)

  Triggers when an item is moved to a group (same or different board).

• Trigger
  New Board

  Triggers when a new board is created.

• Trigger
  New Item in Board

  Triggers when an item is created in a specific board.

• Trigger
  New Subitem on Board

  Triggers when a new subitem on a specific board is created.

• Trigger
  New Update in Board

  Triggers when a new update is posted on a board.

• Trigger
  New User

  Triggers when a new user joins your monday.com account.

• Trigger
  Specific Columns Values Changed in Board

  Triggers when one of the specified columns' value is changed in the selected board.

• Trigger
  Specific Column Value Changed in Board

  Triggers when a specific column's value changes in the selected board.

• Trigger
  Specific Subitem Column Value Changed in Board

  Triggers when a specific column's value changes in a subitem within the selected board.

• Action
  Archive Board

  Archives a board

• Action
  Archive Group

  Archives a specific group in a board

• Action
  Archive Item

  Archives an item

• Action
  Create Board

  Creates a new board

• Action
  Create Column

  Create a new column in board.

• Action
  Create Group

  Creates a new group in a board

• Action
  Create Item

  Create a new Item in a board

• Action
  Create Subitem

  Create a new subitem in a item with column values

• Action
  Create Update

  Create a new update.

• Action
  Delete Group

  Delete a specific group from a board

• Action
  Delete Item

  Delete an item from a board

• Action
  Duplicate Item

  Create a duplicate of an existing item (including subitems). Note: this action takes a few minutes to complete the subitem duplication.

• Action
  Find Items

  Find items that match a specific value in a column

• Action
  Find Subitems

  Finds the subitems of a specific item on the board

• Action
  Find User by Name

  Search for a user by name using exact matching

• Action
  Get Board Values

  Returns the data for a all columns in the specific board

• Action
  Get Column Values

  Returns the data for a specific column in the board

• Action
  Get File Column Values

  Returns the data for a specific file column in the board

• Action
  Get Group Details

  Returns the group name for a specific board

• Action
  Get User Details

  Returns the details for a specific user

• Action
  Group Position

  Duplicate a group with its items

• Action
  List Boards

  Returns a list of your active boards ordered by creation date. Optionally specify a maximum number to return (default 25).

• Action
  Move Item to Group

  Move an item to a different group

• Action
  Update Item

  Change multiple column values of an item

• Action
  Update Item Name

  Update an item's name

• Action
  Update Subitem

  Updates a update subitem on your board.

• Action
  Upload File to Specific Column

  Upload File To Specific Column

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