Connect NetHunt CRM to PandaDoc

Both apps 38NetHunt CRM 16PandaDoc 22

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

  Polling trigger. Fires when a document reaches completed status. Dedup by document id.

• Trigger
  Document completed (instant)

  Instant trigger: fires when a PandaDoc document reaches the completed state. Self-registering — APIANT creates the PandaDoc webhook when you turn the automation on and removes it when you turn it off, so there is nothing to paste. Only document_state_changed events with status document.completed are passed through; each fires once with the document id, name, status, created/modified/completed timestamps and the full document object.

• Trigger
  Document updated

  Polling trigger. Fires when a document is created or changes status. Dedup by document id + date_modified.

• Action
  Change document status

  Manually changes a document's status (e.g. to mark paid or voided). Only certain transitions are allowed.

• Action
  Create contact

  Creates a new contact.

• Action
  Create document from template

  Creates a new document from a template, with recipients, tokens, fields, and pricing tables.

• Action
  Create document link

  Generates a shareable session link for a recipient to view/sign a document.

• Action
  Delete contact

  Deletes a contact by ID.

• Action
  Delete document

  Deletes a document by ID.

• Action
  Download document PDF

  Returns the document as a PDF file. Use watermark options as needed.

• Action
  Find document by name

  Finds a document by name and emits its ID. An error occurs if none or more than one is found.

• Action
  Get document details

  Retrieves detailed data for a single document by ID, including recipients, tokens, fields, and metadata.

• Action
  Get document entered data

  Emits arrays of field and token names and values for the specified document.

• Action
  Get document status

  Returns the current status of a document by ID.

• Action
  Get template details

  Retrieves details for a template by ID, including roles, fields, tokens, and pricing tables.

• Action
  List contacts

  Lists contacts in the workspace.

• Action
  List documents

  Lists documents, optionally filtered by status, template, folder, or search query.

• Action
  List folders

  Lists document folders.

• Action
  List members

  Lists workspace members (users).

• Action
  List templates

  Lists available document templates.

• Action
  Send document

  Moves a draft document to sent status, optionally emailing recipients with a subject and message. Set silent to suppress notifications.

• Action
  Update contact

  Updates an existing contact by ID.

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