Connect Google Drive to NetHunt CRM

Both apps 65Google Drive 49NetHunt CRM 16

• Trigger
  Comment Added (Docs/Sheets/Slides)

  Triggers when a new comment is added to Google Docs, Sheets, or Slides.

• Trigger
  File Created

  Triggers when a new file is created in Google Drive.

• Trigger
  File Deleted or Trashed

  Triggers when a file is moved to trash or permanently deleted in Drive.

• Trigger
  File Shared (Permissions Added)

  Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.

• Trigger
  File Updated

  Triggers when a file's metadata or content changes in Google Drive.

• Trigger
  Google Drive Changes

  Triggers when changes are detected in a Google Drive.

• Trigger
  New File Matching Query

  Triggers when a new Google Drive file matches a provided query. This is the legacy query-centric trigger: it preserves Drive API query config such as ``corpora`` / ``driveId`` aliases and emits the historical ``file_matching_query`` event type. ``FileCreatedTrigger`` covers the broader "new file" case and emits ``file_created``.

• Action
  Add File Sharing Preference

  Modifies sharing permissions for an existing google drive file, granting a specified role to a user, group, domain, or 'anyone'.

• Action
  Copy File

  Duplicates an existing file in google drive, identified by its `file id`.

• Action
  Create Comment

  Tool to create a comment on a file. use when you need to add a new comment to a specific file in google drive.

• Action
  Create File

  Creates a new file or folder with metadata. use to create empty files or folders, or files with content by providing it in the request body (though this action primarily focuses on metadata creation).

• Action
  Create File From Text

  Creates a new file in google drive from provided text content (up to 10mb), supporting various formats including automatic conversion to google workspace types.

• Action
  Create Folder

  Creates a new folder in google drive, optionally within a parent folder specified by its id or name; if a parent name is provided but not found, the action will fail.

• Action
  Create Reply

  Tool to create a reply to a comment in google drive. use when you need to respond to an existing comment on a file.

• Action
  Create Shortcut To File

  Tool to create a shortcut to a file or folder in google drive. use when you need to link to an existing drive item from another location without duplicating it.

• Action
  Delete Comment

  Deletes a comment from a file. use when you need to remove a specific comment from a google drive file.

• Action
  Delete Permission

  Deletes a permission from a file by permission id. use when you need to revoke access for a specific user or group from a file.

• Action
  Delete Reply

  Tool to delete a specific reply by reply id. use when you need to remove a reply from a comment on a file.

• Action
  Download File

  Downloads a file from google drive by its id. for google workspace documents (docs, sheets, slides), optionally exports to a specified `mime type`. for other file types, downloads in their native format regardless of mime type.

• Action
  Edit File

  Updates an existing google drive file by overwriting its entire content with new text (max 10mb).

• Action
  Empty Trash

  Tool to permanently delete all of the user's trashed files. use when you want to empty the trash in google drive.

• Action
  Find File

  Tool to list or search for files and folders in google drive. use when you need to find specific files based on query criteria or list contents of a drive/folder.

• Action
  Find Folder

  Tool to find a folder in google drive by its name and optionally a parent folder. use when you need to locate a specific folder to perform further actions like creating files in it or listing its contents.

• Action
  Generate Ids

  Generates a set of file ids which can be provided in create or copy requests. use when you need to pre-allocate ids for new files or copies.

• Action
  Get About

  Tool to retrieve information about the user, the user's drive, and system capabilities. use when you need to check storage quotas, user details, or supported import/export formats.

• Action
  Get Changes Start Page Token

  Tool to get the starting pagetoken for listing future changes in google drive. use this when you need to track changes to files and folders.

• Action
  Get Comment

  Tool to get a comment by id. use when you need to retrieve a specific comment from a google drive file and have both the file id and comment id.

• Action
  Get File Metadata

  Tool to get a file's metadata by id. use when you need to retrieve the metadata for a specific file in google drive.

• Action
  Get Permission

  Gets a permission by id. use this tool to retrieve a specific permission for a file or shared drive.

• Action
  Get Reply

  Tool to get a specific reply to a comment on a file. use when you need to retrieve the details of a particular reply.

• Action
  Get Revision

  Tool to get a specific revision's metadata by revision id. use when you need to retrieve information about a particular version of a file.

• Action
  Google Drive Delete Folder Or File Action

  Tool to delete a file or folder in google drive. use when you need to permanently remove a specific file or folder using its id. note: this action is irreversible.

• Action
  List Changes

  Tool to list the changes for a user or shared drive. use when you need to track modifications to files and folders, such as creations, deletions, or permission changes. this action requires a `pagetoken` which can be initially obtained using the `get changes start page token` action or from a previous `list changes` response.

• Action
  List Comments

  Tool to list all comments for a file in google drive. use when you need to retrieve comments associated with a specific file.

• Action
  List File Labels

  Tool to list the labels on a file. use when you need to retrieve all labels associated with a specific file in google drive.

• Action
  List Files

  Tool to list a user's files and folders in google drive. use this to search or browse for files and folders based on various criteria.

• Action
  List Permissions

  Tool to list a file's permissions. use when you need to retrieve all permissions associated with a specific file or shared drive.

• Action
  List Replies To Comment

  Tool to list replies to a comment in google drive. use this when you need to retrieve all replies associated with a specific comment on a file.

• Action
  List Revisions

  Tool to list a file's revisions. use when you need to retrieve the revision history of a specific file in google drive.

• Action
  List Shared Drives

  Tool to list the user's shared drives. use when you need to get a list of all shared drives accessible to the authenticated user.

• Action
  Move File

  Tool to move a file from one folder to another in google drive. use when you need to reorganize files by changing their parent folder(s).

• Action
  Parse File

  Deprecated: exports google workspace files (max 10mb) to a specified format using `mime type`, or downloads other file types; use `googledrive download file` instead.

• Action
  Stop Watch Channel

  Tool to stop watching resources through a specified channel. use this when you want to stop receiving notifications for a previously established watch.

• Action
  Update Comment

  Tool to update an existing comment on a google drive file. use when you need to change the content or status (e.g., resolve) of a comment.

• Action
  Update File Put

  Updates file metadata. uses patch semantics (partial update) as per google drive api v3. use this tool to modify attributes of an existing file like its name, description, or parent folders. note: this action currently supports metadata updates only. file content updates require multipart/related upload and are not yet implemented.

• Action
  Update File Revision Metadata

  Updates metadata of a file revision (e.g., keepforever, publish). use this tool to modify the metadata of a specific revision of a file in google drive.

• Action
  Update Permission

  Tool to update a permission with patch semantics. use when you need to modify an existing permission for a file or shared drive.

• Action
  Update Reply

  Tool to update a reply to a comment on a google drive file. use when you need to modify the content of an existing reply.

• Action
  Watch Changes

  Tool to subscribe to changes for a user or shared drive in google drive. use when you need to monitor a google drive for modifications and receive notifications at a specified webhook url.

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