Connect NetHunt CRM to Brevo

Both apps 47NetHunt CRM 16Brevo 31

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

• Trigger
  Company Added

  Triggers when a company is created in Brevo.

• Trigger
  Company Updated

  Triggers when a company is updated in Brevo.

• Trigger
  Contact Added

  Triggers when a Brevo contact is added.

• Trigger
  Contact Subscribed to List (instant)

  Instant trigger — fires when a contact is added to a list (Brevo marketing webhook event listAddition). Self-registering via the Brevo Create/Delete webhook API.

• Trigger
  Contact Unsubscribed

  Triggers when a contact unsubscribes from an email campaign in Brevo.

• Trigger
  Contact Updated (instant)

  Instant trigger — fires when a contact is updated (Brevo marketing webhook event contactUpdated). Self-registering via the Brevo Create/Delete webhook API.

• Trigger
  Deal Added

  Triggers when a deal is created in Brevo.

• Trigger
  Deal Stage Updated

  Triggers when a deal's stage is updated in Brevo.

• Trigger
  Link Clicked

  Triggers when a Brevo contact clicks on any link in a Brevo email campaign.

• Trigger
  Marketing Email Delivered

  Triggers when a Brevo campaign marketing email is delivered.

• Trigger
  Marketing Email Hard Bounced

  Triggers when a Brevo campaign marketing email is hard bounced.

• Trigger
  Marketing Email Opened

  Triggers when a Brevo campaign marketing email is opened.

• Trigger
  New Campaign Status

  Triggers when the status of a Brevo campaign is updated.

• Trigger
  Transactional Email Delivered

  Triggers when a Brevo transactional email is delivered.

• Trigger
  Transactional Email Hard Bounced

  Triggers when a Brevo transactional email is hard bounced.

• Trigger
  Transactional Email Opened

  Triggers when a Brevo transactional email is opened.

• Action
  Add or Update Associations

  Adds or updates associations to companies, deals or contacts in Brevo.

• Action
  Add or Update Company

  Create a new company or update an existing one in Brevo.

• Action
  Add or Update Contact

  Creates or updates a contact. An attribute you map but leave EMPTY is IGNORED - the stored value is preserved, not deleted. Because of that, this action cannot CLEAR an attribute: to empty one, edit it in Brevo directly. Note an explicit null does not clear on Brevo either.

• Action
  Add or Update Deal

  Create a new deal or update an existing one in Brevo.

• Action
  Delete Company

  Deletes the selected company in Brevo, identified by its company ID.

• Action
  Delete Contact

  Deletes the selected contact in Brevo. The contact can be identified by its email address or its contact ID.

• Action
  Delete Deal

  Deletes the selected deal in Brevo, identified by its deal ID.

• Action
  Event Create

  Create event for selected contact.

• Action
  Find Company

  Finds companies in Brevo whose name matches the name you supply. Returns every match, up to 50.

• Action
  Find Deal

  Finds deals in Brevo whose name matches the name you supply. Returns every match, up to 50.

• Action
  Remove Associations

  Removes associations between companies, deals, or contacts in Brevo.

• Action
  Search Contact

  Check if a contact exists in Brevo and fetch the contact details. Contact can be found by email, mobile phone number, Brevo contact ID, external ID, Whatsapp ID and landline number.

• Action
  Send Transactional Email

  Sends an email from your Brevo account with HTML or plain text content.

• Action
  Send Transactional SMS

  Sends an transactional SMS from your Brevo account.

• Action
  Unsubscribe Contact

  Unsubscribe contact from the list(s) he belong to.

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