Integration
Connect NetHunt CRM to EquipDash
When something happens in NetHunt CRM, your agent does the next thing in EquipDash. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want NetHunt CRM and EquipDash to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with NetHunt CRM and EquipDash
Triggers and actions 26 triggers · 43 actions
Trigger
New Call LogTriggered when a new call log is added to a record in the specified folder.
Trigger
New CommentTriggered when a new comment is added to a record in the specified folder.
Trigger
New folderTriggered when a new folder is added.
Trigger
New Google Drive File in FolderPolls 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 FolderTriggered when a record is created or updated in the specified folder.
Trigger
New Record in FolderTriggered when a record is created in the specified folder.
Trigger
Two-way sync new or updated records in folderA 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 FolderTriggered when a record is updated in the specified folder.
Action
Add Call LogAdd a call log to the specified record.
Action
Add CommentAdd a comment to the specified record.
Action
Delete RecordDelete a record by ID.
Action
Find RecordSearch records in a folder by ID or text query.
Action
Find record by field valueFinds 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 FieldsList the fields of a folder.
Action
List Readable FoldersList all folders the user can read.
Action
List Writable FoldersList folders the user can create records in.
Trigger
Booking CancelledTriggers when a booking is cancelled.
Trigger
Booking Checked InTriggers when a booking is checked in.
Trigger
Booking Picked UpTriggers when a booking is picked up.
Trigger
Booking ReturnedTriggers when a booking is returned.
Trigger
Booking Status ChangedTriggers when a booking status changes.
Trigger
Booking UpdatedTriggers when a booking is updated.
Trigger
Customer UpdatedTriggers when a customer is updated.
Trigger
Experience CreatedTriggers when a new experience is created.
Trigger
Experience Schedule CreatedTriggers when an experience schedule is created.
Trigger
Experience UpdatedTriggers when an experience is updated.
Trigger
Inventory AddedTriggers when inventory is added to a product.
Trigger
Inventory UpdatedTriggers when inventory is updated.
Trigger
New CustomerTriggers when a new customer is created.
Trigger
Payment ReceivedTriggers when a payment is received.
Trigger
Product CreatedTriggers when a new product is created.
Trigger
Product UpdatedTriggers when a product is updated.
Trigger
Promo Code CreatedTriggers when a new promo code is created.
Trigger
Shift CreatedTriggers when a new shift is created.
Action
Add Inventory to ProductAdds inventory to a product.
Action
Add Note to BookingAdds a note to a booking.
Action
Add Note to CustomerAdds a note to a customer.
Action
Add Note to WorkshopAdds a note to a workshop item.
Action
Add Payment to BookingAdds a payment to a booking.
Action
Add Pricing to ProductAdds a pricing tier to a product.
Action
Add Schedule to ExperienceAdds a schedule slot to an experience.
Action
Add to WorkshopAdds an item to the workshop.
Action
Archive ExperienceArchives an experience.
Action
Archive ProductArchives a product.
Action
Cancel BookingCancels a booking.
Action
Check Product AvailabilityChecks availability of a product for given dates.
Action
Create BookingCreates a new booking.
Action
Create CustomerCreates a new customer.
Action
Create ExperienceCreates a new experience.
Action
Create Experience CategoryCreates a new experience category.
Action
Create ProductCreates a new product.
Action
Create Product CategoryCreates a new product category.
Action
Create Promo CodeCreates a new promo code.
Action
Create ShiftCreates a new staff shift.
Action
Create TagCreates a new tag.
Action
Create VoucherCreates a new voucher.
Action
Delete CustomerDeletes a customer.
Action
Find CustomerFinds a customer.
Action
Find ExperienceFinds a experience.
Action
Find ProductFinds a product.
Action
Find Promo CodeFinds a promo code.
Action
Find StaffFinds a staff.
Action
Find VoucherFinds a voucher.
Action
Remove From WorkshopRemoves an item from the workshop.
Action
Update Booking StatusUpdates the status of a booking.
Action
Update CustomerUpdates a customer.
Action
Update ExperienceUpdates an experience.
Action
Update ProductUpdates a product.
Action
Update Tags on BookingUpdates the tags on a booking. Provide tag names — existing tags are matched, new tags are created automatically.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews