Connect MailerLite to NetHunt CRM

Both apps 35MailerLite 19NetHunt CRM 16

• Trigger
  Campaign Sent

  Triggers when a campaign has been sent out.

• Trigger
  Spam Complaint

  Triggers when a subscriber issues a spam complaint about an email.

• Trigger
  Subscriber Added to Group

  Triggers when a subscriber is added to a group.

• Trigger
  Subscriber Bounced

  Triggers when an email to a subscriber bounces.

• Trigger
  Subscriber Completed Automation

  Triggers when a subscriber completed a selected workflow.

• Trigger
  Subscriber Created

  Triggers when a subscriber was created on your mailing list.

• Trigger
  Subscriber Fields Updated

  Triggers when the subscriber fields have been updated.

• Trigger
  Subscriber Removed From Group

  Triggers when a subscriber has been removed from a group.

• Trigger
  Subscriber Triggered Automation

  Triggers when a subscriber triggers a selected workflow.

• Trigger
  Subscriber Unsubscribed

  Triggers when a subscriber has unsubscribed from your mailing list.

• Action
  Add Subscriber to a Group

  Add existing subscriber to a specific group by email address.

• Action
  Change Subscriber Email

  Change subscriber email to another.

• Action
  Create a Draft Campaign

  Create a Draft Campaign

• Action
  Create or Update Subscriber

  Create a new subscriber or Update an existing subscriber based on their email.

• Action
  Create Subscribers Group

  Create a new subscribers group.

• Action
  Find a Group

  Search for a group by name

• Action
  Find a Subscriber

  Search for a subscriber by email or name

• Action
  Remove Subscriber From a Group

  Remove subscriber from a specific group by email address.

• Action
  Unsubscribe Subscriber

  Sets the contact's status to "Unsubscribed".

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