Connect NetHunt CRM to DocuPipe

Both apps 32NetHunt CRM 16DocuPipe 16

• 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
  Document Processed

  Triggers when a document finishes parsing and OCR is complete.

• Action
  Add schema

  Creates a new extraction schema in DocuPipe from a JSON schema you supply, and returns its schema ID.

• Action
  Analyze document

  Asks DocuPipe a list of plain-language questions about one document and starts the analysis, returning the analysis ID to fetch the answers with.

• Action
  Classify Document

  Sends one or more documents to DocuPipe to be sorted into your classes, and returns the job that is doing the work.

• Action
  Delete document

  Removes a document from your DocuPipe account.

• Action
  Delete schema

  Removes an extraction schema from your DocuPipe account.

• Action
  Extract Data From Document

  Pulls structured data out of a document using one of your schemas, and returns the extraction to fetch the results with.

• Action
  Find documents by criteria

  Finds documents in your DocuPipe account whose file name or document ID matches what you search for.

• Action
  Get Document

  Returns one document from your DocuPipe account, with its file details, processing status, parsed text and your own metadata.

• Action
  Get Extraction Result

  Returns the data DocuPipe pulled out of a document, shaped by the schema that was used, along with per-field confidence details.

• Action
  Get schema

  Returns one extraction schema from your DocuPipe account, including the JSON schema it applies and its guidelines.

• Action
  List documents

  Returns the documents in your DocuPipe account, optionally narrowed to one dataset or a date range.

• Action
  List extractions

  Returns the data extractions in your DocuPipe account, optionally narrowed to one schema, one document, or a specific set of extractions.

• Action
  List schemas

  Returns the extraction schemas in your DocuPipe account.

• Action
  Upload and Extract Data

  Sends a file to DocuPipe and immediately starts pulling structured data out of it, returning both the new document and the extraction.

• Action
  Upload Document

  Sends a file to DocuPipe to be read and turned into a document you can extract data from.

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