Connect Cliniko to NetHunt CRM

Both apps 64Cliniko 48NetHunt CRM 16

• Trigger
  Cancelled individual appointment

  Triggered when an individual appointment is cancelled.

• Trigger
  New cancelled attendee

  Triggered when an attendee is cancelled.

• Trigger
  New or updated attendee

  Triggered when an attendee is created or updated.

• Trigger
  New or updated business

  Triggered when a business is created or updated.

• Trigger
  New or updated communication

  Triggered when a communication is created or updated.

• Trigger
  New or updated contact

  Triggered when a contact is created or updated.

• Trigger
  New or updated daily availability

  Triggered when a daily availability is created or updated.

• Trigger
  New or updated group appointment

  Triggered when a group appointment is created or updated.

• Trigger
  New or updated individual appointment

  Triggered when an individual appointment is created or updated.

• Trigger
  New or updated invoice

  Triggered when an invoice is created or updated.

• Trigger
  New or updated patient

  Triggered when a patient is created or updated.

• Trigger
  New or updated patient case

  Triggered when a patient case is created or updated.

• Trigger
  New or updated practitioner

  Triggered when a practitioner is created or updated.

• Trigger
  New or updated treatment notes

  Triggered when treatment notes is created or updated.

• Trigger
  Patient added or removed for group appointment in date range

  Triggered when a patient is added or removed for a group appointment within the specified date range.

• Trigger
  Two-way sync new or updated contacts

  A trigger for two-way syncing new and updated contacts, with enhanced on-the-fly mapping. Can only be used with enhanced two-way sync actions that support on-the-fly mapping.

• Trigger
  Two-way sync new or updated patients

  A trigger for two-way syncing new and updated patients, with enhanced on-the-fly mapping. Can only be used with enhanced two-way sync actions that support on-the-fly mapping.

• Action
  Archive patient

  Archives a patient. An error will occur if the patient is not found.

• Action
  Create contact

  Creates a new contact.

• Action
  Create patient

  Creates a new patient.

• Action
  Find Appointment by Patient Id

  Returns appointment details for the specified patient if the Patient ID exists.

• Action
  Find cancelled appointment

  Searches for a cancelled appointment. If no matching appointment is found, an error occurs.

• Action
  Find contact by email

  Returns details of the contact having the specified email address. An error occurs if zero or multiple are found.

• Action
  Find patient by email

  Returns details of the patient having the specified email address. An error occurs if zero or multiple are found.

• Action
  Get appointment

  Returns details of the specified appointment.

• Action
  Get appointments by practitioner ID

  Returns appointment details by practitioner ID.

• Action
  Get appointment type

  Returns details of the specified appointment type.

• Action
  Get appointment type billable item

  Returns details for a billable item.

• Action
  Get billable item

  Returns details of the specified billable item.

• Action
  Get business

  Returns details of the specified business.

• Action
  Get cancelled appointment

  Returns details of the specified cancelled appointment.

• Action
  Get contact

  Returns details of the specified contact.

• Action
  Get group appointment

  Returns details of the specified group appointment.

• Action
  Get group appointment attendees

  Returns attendee information for the specified group appointment.

• Action
  Get individual appointment attendees

  Returns attendee information for the specified individual appointment.

• Action
  Get invoice

  Returns details of the specified invoice.

• Action
  Get patient

  Returns details of the specified patient.

• Action
  Get patient case

  Returns details of the specified patient case.

• Action
  Get patient referral source

  Returns the referral source for the specified patient.

• Action
  Get practitioner

  Returns details of the specified practitioner. An error occurs if not found.

• Action
  Get practitioner availabilities

  Returns availability information for the specified practitioner.

• Action
  List invoices for patient case

  Emits all invoice IDs for the specified patient case.

• Action
  Two-way sync add or update a contact

  An action for two-way syncing new and updated contacts, with enhanced on-the-fly mapping using contact email addresses for matching. Can only be used with enhanced two-way sync triggers that support on-the-fly mapping.

• Action
  Two-way sync add or update a patient

  An action for two-way syncing new and updated patients, with enhanced on-the-fly mapping using patient email addresses for matching. Can only be used with enhanced two-way sync triggers that support on-the-fly mapping.

• Action
  Update contact

  Updates a contact.

• Action
  Update patient

  Updates a patient.

• Action
  Update patient custom field

  Updates the value of the specified custom field for the specified patient.

• Action
  Update patient referral

  Sets or changes a patient's referral source. Choose the referral source type; supply a Referrer ID only for types that take one (e.g. Patient or Contact).

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