Connect NetHunt CRM to ChartMogul

Both apps 40NetHunt CRM 16ChartMogul 24

• 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
  Add a Custom Attribute to a Customer via Email

  Adds a custom attribute to every ChartMogul customer with the given email address.

• Action
  Add a Custom Attribute to a Customer via External ID

  Adds a custom attribute to the ChartMogul customer with the given external ID. Looks the customer up by external ID first, then writes the attribute.

• Action
  Add a Custom Attribute to a Customer via UUID

  Adds a custom attribute to one ChartMogul customer, identified by ChartMogul's customer ID.

• Action
  Add Tags to a Customer via Email

  Adds one or more tags to every ChartMogul customer with the given email address.

• Action
  Add Tags to a Customer via External ID

  Adds one or more tags to the ChartMogul customer with the given external ID. Looks the customer up by external ID first, then writes the tags.

• Action
  Add Tags to a Customer via UUID

  Adds one or more tags to one ChartMogul customer, identified by ChartMogul's customer ID.

• Action
  Create a Contact

  Creates a contact person on a ChartMogul customer.

• Action
  Create a Customer

  Creates a new customer in ChartMogul under one of your data sources.

• Action
  Create an Opportunity

  Creates a sales opportunity (deal) on a ChartMogul customer.

• Action
  Create a Note or Call Log

  Logs a note or a call against a ChartMogul customer.

• Action
  Create a Task

  Creates a task on a ChartMogul customer and assigns it to a team member.

• Action
  List Customer's Opportunities

  Returns the sales opportunities (deals) on a ChartMogul customer.

• Action
  List Customer's Tasks

  Returns the tasks on a ChartMogul customer.

• Action
  Merge Customers

  Merges one ChartMogul customer into another. Identify each side either by its ChartMogul ID or by your own external ID plus its data source.

• Action
  Retrieve a Customer Profile

  Returns one ChartMogul customer's full profile, including its tags and custom attributes.

• Action
  Retrieve a Metric

  Returns one ChartMogul subscription metric over a date range, such as MRR, ARR, customer count or churn rate.

• Action
  Search Contacts

  Finds ChartMogul contacts by email, customer or data source.

• Action
  Search for Customer via Email

  Finds ChartMogul customers by email address.

• Action
  Search for Customer via External ID

  Finds ChartMogul customers by the ID they carry in your own billing system.

• Action
  Update a Contact

  Updates a ChartMogul contact. Only the fields you fill in are changed.

• Action
  Update a Customer

  Updates a ChartMogul customer. Only the fields you fill in are changed.

• Action
  Update an Opportunity

  Updates a ChartMogul sales opportunity. Only the fields you fill in are changed.

• Action
  Update a Note or Call Log

  Updates a note or call log on a ChartMogul customer. Only the fields you fill in are changed.

• Action
  Update a Task

  Updates a task on a ChartMogul customer. Only the fields you fill in are changed.

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