Connect Copper to NetHunt CRM

Both apps 55Copper 39NetHunt CRM 16

• Trigger
  New Activity

  Triggers when a new activity is created.

• Trigger
  New Company

  Triggers when a new Company is created in Copper.

• Trigger
  New Lead

  Triggers when a Lead is created in Copper.

• Trigger
  New Opportunity

  Triggers when an Opportunity is created in Copper.

• Trigger
  New Person

  Triggers when a new Person is created in Copper.

• Trigger
  New Project

  Triggers when a new Project is created in Copper.

• Trigger
  New Task

  Triggers when a new Task is created in Copper.

• Trigger
  Updated Company

  Triggers when a Person's Company is changed.

• Trigger
  Updated Contact Type

  Triggers when a Person's Contact Type is changed.

• Trigger
  Updated Lead

  Triggers when a Lead is changed.

• Trigger
  Updated Lead Status

  Triggers when a Lead's status is changed.

• Trigger
  Updated Opportunity

  Triggers when an Opportunity is changed.

• Trigger
  Updated Opportunity Stage

  Triggers when an Opportunity's stage is changed.

• Trigger
  Updated Opportunity Status

  Triggers when an Opportunity's status is changed.

• Trigger
  Updated Person

  Triggers when a Person is changed.

• Trigger
  Updated Project

  Triggers when a Project is changed.

• Trigger
  Updated Task

  Triggers when a Task is changed.

• Action
  Associate to Project

  This Action allows you to relate an existing Project to and existing CRM object; both objects have to exist before you run this Action. This Action expects two ID's for input: the ID of the CRM record you want to relate to and the Project ID you want to relate it with. This Action was designed to be used in multi-step Zaps, where you already have a Project ID and an related record ID (e.g. a Person) from previous steps.

• Action
  Create Activity

  Logs a new Activity on a Person, Company, Opportunity, or Lead.

• Action
  Create Company

  Creates a new Company.

• Action
  Create Lead

  Creates a new Lead.

• Action
  Create Opportunity

  Creates a new Opportunity.

• Action
  Create Person

  Creates a new Person.

• Action
  Create Project

  Creates a new Project.

• Action
  Create Task

  Creates a new Task.

• Action
  Create/Update Company

  Creates or Updates a Company depending on the match criteria.

• Action
  Create/Update Lead

  Creates or Updates a Lead depending on the match criteria.

• Action
  Create/Update Opportunity

  Creates or Updates an Opportunity based off of a match criteria.

• Action
  Create/Update Person

  Creates or Updates a Person depending on the match criteria.

• Action
  Create/Update Project

  Creates or Updates a Project depending on the match criteria.

• Action
  Search for a Company

  Searches for an existing company in Copper.

• Action
  Search for an Activity

  Searches for an existing activity in Copper.

• Action
  Search for a Opportunity

  Searches for an existing opportunity in Copper.

• Action
  Search for a Person

  Searches for an existing person in Copper.

• Action
  Search for a Project

  Searches for an existing project in Copper.

• Action
  Update Company

  Updates a Company depending on the match criteria.

• Action
  Update Opportunity

  Updates an Opportunity based off of a match criteria.

• Action
  Update Person

  Updates a Person depending on the match criteria.

• Action
  Update Project

  Updates a Project depending on the match criteria.

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