Connect NetHunt CRM to Anysite

Both apps 39NetHunt CRM 16Anysite 23

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

• Action
  Find Amazon products by search criteria

  Search Amazon product listings by keyword.

• Action
  Find Google Maps places by search criteria

  Search Google Maps for places by keyword and location.

• Action
  Find LinkedIn jobs by keywords

  Search LinkedIn job postings by keyword, location, or other criteria.

• Action
  Find LinkedIn users by keywords

  Search LinkedIn for users matching a name, title, or other criteria.

• Action
  Find Reddit posts by search criteria

  Search Reddit posts by keyword or subreddit.

• Action
  Find TikTok videos by search criteria

  Search TikTok videos by keyword or hashtag.

• Action
  Find X posts by search criteria

  Search X (Twitter) posts by keyword or other criteria.

• Action
  Find Yelp businesses by term

  Search Yelp businesses by keyword and location.

• Action
  Find YouTube videos by search criteria

  Search YouTube videos by keyword.

• Action
  Get Amazon product

  Fetch structured product data (price, rating, details) for an Amazon listing by URL or ASIN.

• Action
  Get Glassdoor company ratings

  Fetch structured ratings and review summary for a company on Glassdoor.

• Action
  Get Google Maps place

  Fetch structured place details (hours, rating, address) from Google Maps by place ID or URL.

• Action
  Get Instagram profile

  Fetch structured profile data for an Instagram user by username.

• Action
  Get LinkedIn company

  Fetch structured company data for a LinkedIn company page by URL.

• Action
  Get LinkedIn profile

  Fetch structured profile data for a LinkedIn user by profile URL.

• Action
  Get Reddit post

  Fetch structured data for a Reddit post by URL, including comments.

• Action
  Get TikTok profile

  Fetch structured profile data for a TikTok user by username.

• Action
  Get TikTok video

  Fetch structured data for a TikTok video by URL.

• Action
  Get X post

  Fetch structured data for an X (Twitter) post by URL or ID.

• Action
  Get X profile

  Fetch structured profile data for an X (Twitter) user by username.

• Action
  Get Yelp business

  Fetch structured business details from Yelp by business URL or ID.

• Action
  Get YouTube channel

  Fetch structured data for a YouTube channel by URL or handle.

• Action
  Get YouTube video

  Fetch structured data for a YouTube video by URL or ID.

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