Connect JotForm to NetHunt CRM

Both apps 53JotForm 37NetHunt CRM 16

• Trigger
  New Form Submission

  Polling trigger: fires when a new submission is received for the specified form.

• Trigger
  New Form Submission (instant)

  Fires instantly via a self-registered JotForm webhook whenever the selected form receives a new submission. Instant alternative to the New Form Submission poller — the platform registers the webhook on activation and removes it on deactivation.

• Action
  Add New Question to Specified Form

  Add new question to specified form

• Action
  Add or Edit a Single Question Properties

  Add or edit a single question properties

• Action
  Add Resources to Label

  Add Resources to Label

• Action
  Add Submissions to the Form

  Add Submissions to the Form

• Action
  Clone Form

  Clone an existing form.

• Action
  Create Folder

  Create Folder

• Action
  Create Form

  Create a new form

• Action
  Create or Replace Form

  Create new forms

• Action
  Create Report

  Create report

• Action
  Create Submission

  Add a new submission to a form. Provide answers keyed by submission[<qid>] field names.

• Action
  Delete a Report

  Delete a Report

• Action
  Delete Folder

  Delete Folder

• Action
  Delete Form

  Delete a form (moves to trash).

• Action
  Delete Form Question

  Delete Form Question

• Action
  Delete Submission

  Delete a single submission.

• Action
  Edit Submission Data

  Edit Submission Data

• Action
  Get Details About a Question

  Get Details About a Question

• Action
  Get Folder

  Get details of a specific folder including the forms it contains.

• Action
  Get Form

  Get the details of a specific form.

• Action
  Get Form Files

  List files uploaded to a form's submissions.

• Action
  Get Form Questions

  Get a list of all questions on a form.

• Action
  Get History

  Get History

• Action
  Get Label Resources

  Get Label Resources

• Action
  Get Report Details

  Get Report Details

• Action
  Get Submission

  Get details of a specific submission.

• Action
  Get User Reports

  Get User Reports

• Action
  List Account Submissions

  List all submissions across all forms on the account.

• Action
  List Folders

  Get a list of form folders on the account.

• Action
  List Form Reports

  List all reports for a specific form.

• Action
  List Forms

  List all forms on the account.

• Action
  List Form Submissions

  List submissions for a specific form.

• Action
  Remove Resources from Label

  Remove Resources from Label

• Action
  Replace Form Properties

  Add or edit properties of a specific form

• Action
  Set Form Properties

  Add or edit properties of a specific form

• Action
  Update Folder

  Update Folder

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