Connect NetHunt CRM to folk

Both apps 43NetHunt CRM 16folk 27

• 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
  Company Added

  Triggers when a new company is created or added to a group.

• Trigger
  Company Custom Field Updated

  Triggers when a company custom field (for example tag, status, text, assignee) is updated.

• Trigger
  Company Removed

  Triggers when a company is deleted from the workspace or removed from a group.

• Trigger
  Company Updated

  Triggers when a company basic field (like name, email or URL) in a group is updated.

• Trigger
  Deal Added

  Fires when a new deal is created. Poll GET /v1/deals sorted by creation date.

• Trigger
  Deal Removed

  Fires when a deal is deleted from a pipeline.

• Trigger
  Deal Updated

  Fires when a deal is updated (stage change, field update). Poll GET /v1/deals sorted by update date.

• Trigger
  Person Added

  Triggers when a new person is created or added to a group.

• Trigger
  Person Custom Field Updated

  Triggers when a person custom field (for example tag, status, text, assignee) is updated.

• Trigger
  Person Removed

  Triggers when a person is deleted from the workspace or removed from a group.

• Trigger
  Person Updated

  Triggers when a person basic field (like first name, job title, email or URL) in a group is updated.

• Action
  Create Company

  Creates a company in folk, optionally adding it to a group and setting that group's custom fields.

• Action
  Create Deal

  Creates a deal in a folk group, optionally linked to companies and people, and sets that deal type's custom fields.

• Action
  Create Group

  Creates a group in folk. A default "All people" table view is added to the group automatically.

• Action
  Create Note

  Creates a note on a folk person, company or deal. Optionally posts it as a reply to an existing note.

• Action
  Create Person

  Creates a person in folk, optionally adding them to a group and setting that group's custom fields.

• Action
  Create Reminder

  Creates a reminder on a folk person, company or deal, scheduled with an iCalendar recurrence rule.

• Action
  Delete Company

  Deletes a company from folk by its id.

• Action
  Delete Person

  Deletes a person from folk by their id. This also removes their custom fields, notes and associations.

• Action
  Find a Company

  Searches folk companies by name, email or website and returns the matches, with the first one broken out for easy mapping.

• Action
  Find a Person

  Searches folk people by email, full name or phone and returns the matches, with the first one broken out for easy mapping.

• Action
  Get a Company

  Fetches one folk company by id, including its custom field values.

• Action
  Get a Note

  Fetches one folk note by id, with its text, author and the record it is attached to.

• Action
  Get a Person

  Fetches one folk person by id, including their custom field values.

• Action
  List Groups

  Returns the groups in the folk workspace, with each group's id, name and visibility.

• Action
  Update Company

  Updates a folk company. Only the fields you fill in are changed; list fields such as emails replace the whole list.

• Action
  Update Person

  Updates a folk person. Only the fields you fill in are changed; list fields such as emails replace the whole list.

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