Connect Booqable to NetHunt CRM

Both apps 39Booqable 23NetHunt CRM 16

• Trigger
  Completed Payment

  Triggers when a payment is completed.

• Trigger
  Finalize Invoice

  Triggers when an invoice is finalized.

• Trigger
  New Customer

  Triggers when a new customer is added.

• Trigger
  New Product

  Fires when a new product is created in the catalog. Poll GET /api/boomerang/products sorted by created_at.

• Trigger
  Reserved Order

  Triggers when an order is reserved.

• Trigger
  Started Order

  Triggers when an order is started.

• Trigger
  Stopped Order

  Triggers when an order is stopped.

• Trigger
  Updated Order

  Triggers when an order is updated.

• Action
  Create Coupon

  Creates a discount coupon in Booqable with a code, a discount type and value, and optional validity dates, redemption limits and eligible items.

• Action
  Create Customer

  Creates a customer in Booqable with name, email and billing defaults, plus any of the account's own customer custom fields.

• Action
  Create Order

  Creates a rental order in Booqable for a customer over a rental period, with pickup or delivery locations, deposit and discount settings, and any of the account's own order custom fields.

• Action
  Find Customer - By ID

  Returns one Booqable customer by its id, including the account's own customer custom fields.

• Action
  Find Customer - By Name or Email

  Finds Booqable customers whose name contains the text you give, or whose email matches exactly. Give either one or both.

• Action
  Find Order - By ID

  Returns one Booqable order by its id, including totals, rental period, locations and the account's own order custom fields.

• Action
  Find Product - By ID

  Returns one Booqable product by its id, including pricing, tracking settings and the product group's custom fields.

• Action
  List Customers

  Returns a page of Booqable customers, newest or sorted as you choose, with each customer's core details and custom field values.

• Action
  List Documents

  Returns a page of Booqable documents - invoices, quotes, contracts and packing slips - optionally narrowed to one document type, order or customer.

• Action
  List Locations

  Returns the rental locations set up in Booqable, with their addresses and whether pickup or delivery is enabled.

• Action
  List Orders

  Returns a page of Booqable orders with their rental period, status and totals, optionally narrowed to one status or customer.

• Action
  List Payments

  Returns a page of Booqable payments - charges, authorizations and refunds - optionally narrowed to one order or customer.

• Action
  List Products

  Returns a page of Booqable products with their pricing and tracking settings, optionally narrowed to one product group.

• Action
  List Stock Items

  Returns a page of Booqable stock items with their identifier, status and location, optionally narrowed to one product, product group or location.

• Action
  Update Customer

  Updates an existing Booqable customer. Fields you leave blank keep their current values, including custom fields.

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