Connect Files.com to NetHunt CRM

Both apps 39Files.com 23NetHunt CRM 16

• Trigger
  Automation Run Completed

  Triggered when a run of the selected Files.com automation finishes, whether it succeeded, failed or was canceled. Each run is reported once, after it completes.

• Trigger
  File Deleted

  Triggered when a file or folder is deleted in Files.com. Reports the path that was deleted and who deleted it.

• Trigger
  Group Created

  Triggered when a new group is created in Files.com. Reports the group's name, members and login permissions.

• Trigger
  New File or Folder Created

  Triggered when a file or folder is created in Files.com, whether uploaded, copied or created by an automation. Reports the new path and who created it.

• Trigger
  New File Uploaded

  Triggered when a new file appears in the folder you choose. Reports the file's path, name, size and last-modified time.

• Trigger
  Share Link Created

  Triggered when a new share link is created in Files.com. Reports the link's public address, what it shares and when it expires.

• Trigger
  User Created

  Triggered when a new user is created in Files.com. Reports the user's name, username, email and login permissions.

• Action
  Add User to Group

  Adds an existing Files.com user to a group, optionally as a group administrator. Returns the new group membership, including the group name and the user's username.

• Action
  Copy File

  Copies a file or folder in Files.com to a new path, leaving the original in place. Returns the copy status, plus a migration ID when a large copy continues in the background.

• Action
  Create Folder

  Creates a folder at the given path in Files.com, optionally creating any missing parent folders. Returns the new folder's path, name and creation details.

• Action
  Create Group

  Creates a group in Files.com, optionally with its starting members, group administrators and login-protocol permissions. Returns the new group including its ID.

• Action
  Create Share Link

  Creates a public share link for one or more files or folders in Files.com, optionally password-protected, expiring or use-limited. Returns the link's public address.

• Action
  Delete File

  Deletes a file or folder from Files.com at the given path. Deleting a folder that still has contents requires the recursive option.

• Action
  Delete Folder

  Deletes a folder from Files.com at the given path. Use the recursive option to delete a folder that still has files or subfolders in it.

• Action
  Delete Group

  Deletes a group from Files.com by its ID. The group's members keep their own accounts; only the group is removed.

• Action
  Delete User

  Deletes a user from Files.com by their ID, removing their access to the site.

• Action
  Download File

  Gets a temporary download address for a file in Files.com, along with the file's name, size and checksums. Pass the download address to a later step to fetch or attach the file.

• Action
  List Folder Contents

  Lists the files and folders inside a Files.com folder, with each item's path, name, type, size and last-modified time.

• Action
  Move File

  Moves or renames a file or folder in Files.com to a new path. The original path no longer exists afterwards.

• Action
  Remove User from Group

  Removes a user from a Files.com group. Looks up the membership for the group and user you name, then removes it.

• Action
  Run Automation

  Starts a run of the Files.com automation you choose, the same as pressing Run in Files.com. The run continues in the background.

• Action
  Update User

  Updates a Files.com user's details, login permissions and access settings. Fields you leave blank keep their current values.

• Action
  Upload File

  Uploads a file into Files.com at the path you choose, fetching the bytes from the file's web address. Returns the stored file's path, name and size.

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