Connect Capsule CRM to NetHunt CRM

Both apps 86Capsule CRM 70NetHunt CRM 16

• Trigger
  List projects

  list projects (cases/kases), surfacing new ones over time

• Trigger
  List tasks

  list tasks, surfacing new ones over time

• Trigger
  New case

  Polls for newly created cases in Capsule CRM.

• Trigger
  New opportunity

  Polls for newly created opportunities in Capsule CRM.

• Trigger
  New organization

  Polls for newly created organizations in Capsule CRM.

• Trigger
  New person

  Polls for newly created people in Capsule CRM.

• Trigger
  New task

  Polls for newly created tasks in Capsule CRM.

• Trigger
  New user

  Polls for newly created user accounts in Capsule CRM.

• Action
  Add additional party to opportunity

  add an additional party to an opportunity

• Action
  Add Task

  Add a task in Capsule CRM (POST /api/v2/tasks), optionally linked to a party.

• Action
  Complete a task

  Marks a task as completed in Capsule CRM.

• Action
  Create a case

  Creates a new case (kase) in Capsule CRM, optionally linked to a party.

• Action
  Create a new task for organization

  This action creates a new task for the specified organization.

• Action
  Create an open case for organization

  This action creates a new open case for the specified organization.

• Action
  Create an open case for person

  This action creates a new open case for the specified person.

• Action
  Create an organization

  Creates a new organization party in Capsule CRM.

• Action
  Create a note

  Creates a new note (entry) attached to a party, opportunity, or case in Capsule CRM.

• Action
  Create a person

  Creates a new person party in Capsule CRM.

• Action
  Create a tag for organization

  This action creates a new tag for the specified organization.

• Action
  Create a tag for person

  This action creates a new tag for the specified person.

• Action
  Create entry

  create an activity entry

• Action
  Create opportunity

  create an opportunity

• Action
  Create party

  create a party (person or organization)

• Action
  Create project

  create a project (case)

• Action
  Create tag

  create a tag for an entity type

• Action
  Delete a party

  Deletes a party by id in Capsule CRM.

• Action
  Delete entry

  delete an activity entry

• Action
  Delete opportunity

  delete an opportunity

• Action
  Delete project

  delete a project

• Action
  Delete tag

  delete a tag

• Action
  Delete task

  delete a task

• Action
  Get Party

  Get a party (person or organization) in Capsule CRM, including its custom fields both raw and flattened by field-definition id.

• Action
  List additional parties for opportunity

  list additional parties on an opportunity

• Action
  List cases

  Lists cases (kases) in Capsule CRM.

• Action
  List deleted opportunities

  list deleted opportunities

• Action
  List deleted parties

  list deleted parties

• Action
  List deleted projects

  list deleted projects

• Action
  List employees of party

  list people employed at an organization party

• Action
  List entries by date

  list activity entries by date

• Action
  List entries for entity

  list activity entries for a party/opportunity/project

• Action
  List opportunities

  Lists sales opportunities in Capsule CRM.

• Action
  List opportunities by party

  list opportunities for a party

• Action
  List parties

  Lists parties (people and organizations) in Capsule CRM.

• Action
  List projects associated with opportunity

  list projects associated with an opportunity

• Action
  List projects by party

  list projects for a party

• Action
  List tags

  list tags for an entity type

• Action
  List teams

  list teams

• Action
  List tracks for entity

  list tracks for an entity

• Action
  List users

  list users

• Action
  Remove additional party from opportunity

  remove an additional party from an opportunity

• Action
  Run filter query

  run a saved/ad-hoc filter query for an entity

• Action
  Search opportunities

  search opportunities

• Action
  Search parties

  Searches parties by a free-text query in Capsule CRM.

• Action
  Search projects

  search projects

• Action
  Show current user

  get the authenticated user

• Action
  Show entry

  retrieve an activity entry by ID

• Action
  Show opportunity

  retrieve an opportunity by ID

• Action
  Show project

  retrieve a project by ID

• Action
  Show site config

  get account/site configuration

• Action
  Show tag

  retrieve a tag by ID

• Action
  Show task

  retrieve a task by ID

• Action
  Show user

  retrieve a user by ID

• Action
  Update entry

  update an activity entry

• Action
  Update opportunity

  update an opportunity

• Action
  Update party

  update a party

• Action
  Update project

  update a project

• Action
  Update tag

  update a tag

• Action
  Update task

  update a task

• Action
  Update user

  update a user

• Action
  Upload attachment

  upload an attachment

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