Connect NetHunt CRM to Postman

Both apps 47NetHunt CRM 16Postman 31

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

  Triggered when a new collection is created.

• Trigger
  New Environment

  Triggers when you need to list environments. Optionally filter by workspace.

• Trigger
  New Mock Server

  Triggers when you need to list mock servers. Optionally filter by workspace.

• Trigger
  New Monitor

  Triggered when a new monitor is created in Postman.

• Trigger
  New Workspace

  Triggered when a new workspace is created.

• Action
  Create Collection

  Creates a new Postman collection.

• Action
  Create Environment

  Creates a new Postman environment with optional variables.

• Action
  Create Folder

  Creates a folder inside a collection.

• Action
  Create Mock Server

  Creates a new mock server from a collection.

• Action
  Create Monitor

  Creates a new Postman monitor for a collection.

• Action
  Create Request

  Creates a new request in a Postman collection.

• Action
  Create Workspace

  Creates a new Postman workspace.

• Action
  Delete Collection

  Delete a collection by ID. DELETE https://api.getpostman.com/collections/{collectionId}

• Action
  Delete Environment

  Delete an environment by ID. DELETE https://api.getpostman.com/environments/{environmentId}

• Action
  Delete Mock Server

  Delete a mock server by ID. DELETE https://api.getpostman.com/mocks/{mockId}

• Action
  Delete Monitor

  Delete a monitor by ID. DELETE https://api.getpostman.com/monitors/{monitorId}

• Action
  Delete Workspace

  Delete a workspace by ID. DELETE https://api.getpostman.com/workspaces/{workspaceId}

• Action
  Find Collection by ID

  Returns a single collection by ID.

• Action
  Find Environment by ID

  Returns a single environment by ID.

• Action
  Find Mock Server by ID

  Returns a single mock server by ID.

• Action
  Find Monitor by ID

  Returns a single monitor by ID.

• Action
  Find Workspace by ID

  Returns a single workspace by ID.

• Action
  List Collections

  List all collections accessible to the API key, optionally filtered by workspace. GET https://api.getpostman.com/collections?workspace={id}

• Action
  List Environments

  List all environments accessible to the API key, optionally filtered by workspace. GET https://api.getpostman.com/environments?workspace={id}

• Action
  List Workspaces

  List all workspaces accessible to the API key. GET https://api.getpostman.com/workspaces

• Action
  Run Monitor

  Runs a Postman monitor and returns the run results.

• Action
  Update Collection

  Replaces an existing collection with the name, requests and settings you supply.

• Action
  Update Environment

  Updates an existing environment.

• Action
  Update Mock Server

  Update a mock server's config. PUT https://api.getpostman.com/mocks/{mockId}

• Action
  Update Monitor

  Updates an existing monitor.

• Action
  Update Workspace

  Updates an existing workspace.

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