Connect Float to NetHunt CRM

Both apps 52Float 36NetHunt CRM 16

• Trigger
  New Allocation

  Triggers when a new allocation is created.

• Trigger
  New Client

  Triggers when a new client is added.

• Trigger
  New Department

  Triggers when a new department is added.

• Trigger
  New Logged Time

  Triggers when a new logged time is created.

• Trigger
  New Milestone

  Triggers when a new milestone is created.

• Trigger
  New Person

  Triggers when a new person is added.

• Trigger
  New Phase

  Triggers when a new phase is created.

• Trigger
  New Project

  Triggers when a new project is created.

• Trigger
  New Project Task

  Triggers when a new project task is created.

• Trigger
  New Time Off

  Triggers when a new time off is created.

• Trigger
  Updated Allocation

  Triggers when an allocation is modified.

• Trigger
  Updated Logged Time

  Triggers when a logged time is modified.

• Trigger
  Updated Phase

  Triggers when a phase is modified.

• Trigger
  Updated Project

  Triggers when a project is modified.

• Trigger
  Updated Project Task

  Triggers when a project task is modified.

• Action
  Create Allocation

  Creates a new allocation.

• Action
  Create Client

  Creates a new client.

• Action
  Create Department

  Creates a new department.

• Action
  Create Logged Time

  Creates a new logged time.

• Action
  Create Milestone

  Creates a new milestone.

• Action
  Create Person

  Creates a new person.

• Action
  Create Phase

  Creates a new phase.

• Action
  Create Project

  Creates a new project.

• Action
  Create Project Task

  Creates a new project task.

• Action
  Create Time Off

  Creates a new time off.

• Action
  Find Allocation

  Finds an allocation by ID.

• Action
  Find Logged Time

  Finds a logged time by ID.

• Action
  Find Person

  Finds a person by ID, email, or tag(s).

• Action
  Find Project

  Finds a project by ID, project_code, or tag(s).

• Action
  Update Allocation

  Update an existing allocation by ID.

• Action
  Update Logged Time

  Update an existing logged time entry by ID.

• Action
  Update Milestone

  Update an existing milestone by ID.

• Action
  Update Person

  Update an existing person by ID.

• Action
  Update Phase

  Update an existing phase by ID.

• Action
  Update Project

  Update an existing project by ID.

• Action
  Update Project Task

  Update an existing project task by ID.

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