Connect OnceHub to NetHunt CRM

Both apps 48OnceHub 32NetHunt CRM 16

• Trigger
  Booking Canceled

  Triggers when a OnceHub booking is canceled by the customer or by someone on your team.

• Trigger
  Booking Cancelled and Rescheduled

  Triggers when a customer cancels a OnceHub booking and then reschedules it on a different booking page.

• Trigger
  Booking Completed

  Triggers when a OnceHub booking's end time has passed and the meeting is marked completed.

• Trigger
  Booking Lifecycle Event

  Triggers on any OnceHub booking event — scheduled, rescheduled, reassigned, canceled, completed or no-show — with the event name included so you can branch on it.

• Trigger
  Booking No-Show

  Triggers when a OnceHub booking is marked as a no-show.

• Trigger
  Booking Rescheduled

  Triggers when a OnceHub booking is rescheduled to a new time.

• Trigger
  Booking Scheduled

  Triggers when a new OnceHub booking is scheduled.

• Trigger
  Contact Captured

  Triggers when a new contact is captured in OnceHub.

• Trigger
  Contact Lifecycle Event

  Triggers whenever a OnceHub contact is created or changed, so you catch the whole contact lifecycle in one place.

• Trigger
  Contact Updated

  Triggers when an existing OnceHub contact is updated.

• Trigger
  Conversation Abandoned

  Triggers when a website visitor stops replying to a OnceHub chatbot for more than ten minutes and the conversation is abandoned.

• Trigger
  Conversation Closed

  Triggers when a OnceHub chatbot conversation is closed.

• Trigger
  Conversation Lifecycle Event

  Triggers on any OnceHub conversation event — started, closed or abandoned — with the event name included so you can branch on it.

• Trigger
  Conversation Started

  Triggers when a website visitor sends their first message to a OnceHub chatbot and a conversation starts.

• Trigger
  Reassigned Booking

  Triggers when a OnceHub booking is reassigned to a different host.

• Action
  Cancel Booking

  Cancels a OnceHub booking, optionally with a reason and without emailing the customer.

• Action
  Create Contact

  Creates a new contact in OnceHub. Give at least an email address or a mobile number.

• Action
  Create One-Time Booking Link

  Creates a one-time booking link for a published OnceHub booking calendar, optionally prefilling the booking form and pinning the host or duration.

• Action
  Delete Contact

  Deletes a contact from OnceHub.

• Action
  Find Contact

  Finds a OnceHub contact by email address.

• Action
  Get Available Time Slots

  Returns the open meeting times on a OnceHub booking calendar for the window you choose.

• Action
  Get Booking Calendar

  Returns one OnceHub booking calendar with its host, public link and meeting length.

• Action
  Get Booking Details

  Returns one OnceHub booking with its time, customer details and booking form answers.

• Action
  Get Contact

  Returns one OnceHub contact with its details and custom fields.

• Action
  Get Contact's Future Meetings

  Returns a contact's upcoming OnceHub meetings — the bookings that start after the time you give.

• Action
  List Booking Calendars

  Lists the booking calendars in your OnceHub account.

• Action
  List Bookings

  Lists OnceHub bookings, with optional filters for status, contact, host, calendar and date range.

• Action
  List Contacts

  Lists the contacts in your OnceHub account, with optional email and date filters.

• Action
  Mark Booking as No-Show

  Marks a OnceHub booking as a no-show.

• Action
  Reassign Booking

  Reassigns a OnceHub booking to a different host, optionally naming the video conferencing service to use.

• Action
  Request Reschedule

  Asks the customer to pick a new time for a OnceHub booking, optionally telling them why.

• Action
  Update Contact

  Updates an existing OnceHub contact. Only the fields you fill in are changed; anything left blank keeps its current value.

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