Connect NetHunt CRM to Easymailing

Both apps 43NetHunt CRM 16Easymailing 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.

• Action
  Add Member to Automation Queue

  Add member to automation queue. Starts the automation for the member.

• Action
  Add Member to Group

  Add member to group in a specified audience.

• Action
  Cancel Order

  The status of the order will be set to "cancelled". You can use to send an email to the customer to inform him that his order has been cancelled.

• Action
  Create a Campaign

  Creates a campaign draft.

• Action
  Create a Group

  Creates a group in the selected audience.

• Action
  Create a New Cart (Order)

  Creates a new order with status cart in the store.

• Action
  Create or Update Category

  Creates or updates a category in a store.

• Action
  Create or Update Customer

  Creates or updates a customer in a store.

• Action
  Create or Update Member

  Creates or updates a member in a specified audience.

• Action
  Create or Update Product

  Creates or updates a product in a store.

• Action
  Create or Update Variant

  Creates or updates a variant in a store.

• Action
  Delete a Member

  Delete a member in a specified audience.

• Action
  Delete Order

  Delete an order in the selected store.

• Action
  Get Audience

  Get one audience by uuid. GET /audiences/{uuid}.

• Action
  Get Customer by Email

  Finds a customer in an store by their email address.

• Action
  Get Member by Email

  Finds a member in an audience by their email address.

• Action
  List Members

  List members of an audience with pagination. GET /audiences/{audienceUuid}/members.

• Action
  List Orders

  List orders in a store. GET /stores/{storeResourceId}/orders.

• Action
  List Products

  List products in a store. GET /stores/{storeResourceId}/products.

• Action
  Pay Order

  The status of the order will be set to "paid". Orders Paid not trigger the abandoned cart automation and Payment reminder automation.

• Action
  Process Order

  Convert a cart to an order. The status of the order will be set to "new".

• Action
  Refund Order

  The status of the order will be set to "refunded". You can use to send an email to the customer to inform him that his order has been refunded.

• Action
  Remove Member From Group

  Remove member from group in a specified audience.

• Action
  Schedule a Campaign

  Schedules a campaign to be sent at a later date.

• Action
  Send a Campaign

  Sends a campaign now

• Action
  Ship Order

  The status of the order will be set to "shipped". You can use to send an email to the customer to inform him that his order has been shipped.

• Action
  Unsubscribe a Member

  Unsubscribe a member in a specified audience.

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