Connect ComplyCube to NetHunt CRM

Both apps 56ComplyCube 40NetHunt CRM 16

• Trigger
  New Event

  Triggers when a new event is received.

• Action
  Add Note

  Add a note to a client for investigations, reviews, or compliance reporting.

• Action
  Create Address

  Creates a new address for a client.

• Action
  Create Check

  Create a verification check (identity, document, AML, or other check type) against a client.

• Action
  Create Client

  Updates clients details using the given input.

• Action
  Create Document

  Creates a new document for a client.

• Action
  Create Session

  Creates a verification session link using workflow templates.

• Action
  Delete Address

  Deletes an existing address.

• Action
  Delete Client

  Deletes an existing client.

• Action
  Delete Document

  Deletes an existing document.

• Action
  Delete Note

  Delete a note.

• Action
  Find Addresses

  Search and verify an address for KYC address checks.

• Action
  Find Companies

  Search for companies by name or registration details for KYB checks.

• Action
  Generate Check Report

  Generate a PDF report for a specific check.

• Action
  Generate Client Report

  Generate a PDF report summarizing a client's compliance record.

• Action
  Generate Session Report

  Generates a session report PDF and returns it as a file for use in later Zap steps.

• Action
  Generate Token

  Generate an SDK token to securely authenticate a frontend user session.

• Action
  Get Address

  Retrieves an address using "Address ID".

• Action
  Get Check Results

  Retrieves a check's results using "Check ID".

• Action
  Get Client

  Retrieves a client's results using "Client ID".

• Action
  Get Company Details

  Retrieve detailed information about a company by its ID.

• Action
  Get Document

  Retrieves a document using "Document ID".

• Action
  Get Live Photo

  Retrieve a client's live photo by ID.

• Action
  Get Note

  Retrieve a note by ID.

• Action
  Get Risk Profile

  Retrieve a client's AML risk profile and score.

• Action
  Get Session Results

  Retrieves a session's results using "Session ID".

• Action
  List Addresses

  List addresses linked to a client.

• Action
  List Checks

  List checks performed on a client.

• Action
  List Clients

  List clients with optional filters and pagination.

• Action
  List Documents

  List documents linked to a client.

• Action
  List Live Photos

  List a client's live photos.

• Action
  List Notes

  List notes linked to a client.

• Action
  List Workflow Sessions

  List a client's workflow sessions.

• Action
  Update Address

  Updates an existing address.

• Action
  Update Check

  Update an existing check's parameters.

• Action
  Update Client

  Updates clients details using the given input.

• Action
  Update Document

  Updates an existing document.

• Action
  Update Note

  Update an existing note.

• Action
  Upload Document Image

  Uploads an image attachment (front or back) to an existing document.

• Action
  Upload Live Photo

  Upload a client's live photo (selfie) for biometric identity and liveness verification.

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