Connect Userflow to NetHunt CRM

Both apps 35Userflow 19NetHunt CRM 16

• Trigger
  Checklist Completed

  Triggered when a user finishes every task in a Userflow checklist.

• Trigger
  Checklist Dismissed/Ended

  Triggered when a Userflow checklist ends for a user — because they dismissed it, it was completed, or it stopped applying to them. The reason is in checklist_end_reason.

• Trigger
  Checklist Started

  Triggered when a user starts a Userflow checklist. Why it started is in checklist_start_reason.

• Trigger
  Checklist Task Completed

  Triggered when a user completes a single task inside a Userflow checklist.

• Trigger
  Event Tracked

  Triggered when Userflow tracks an event for a user — either your own custom events or Userflow's own flow and checklist events. Name one event to watch, or leave it blank to fire for all of them.

• Trigger
  Flow Completed

  Triggered when a user completes a Userflow flow by reaching its goal step.

• Trigger
  Flow Dismissed/Ended

  Triggered when a Userflow flow ends for a user — because they dismissed it, finished it, or it stopped applying. The reason is in flow_end_reason.

• Trigger
  Flow Started

  Triggered when a user starts a Userflow flow. Why it started is in flow_start_reason.

• Trigger
  Group Created/Updated

  Triggered when a group (a company or account) is created or changed in Userflow.

• Trigger
  Launcher Activated

  Triggered when a user clicks a Userflow launcher (a beacon, button or hotspot) to open it.

• Trigger
  Launcher Dismissed

  Triggered when a user dismisses a Userflow launcher (a beacon, button or hotspot).

• Trigger
  Launcher Seen

  Triggered when a Userflow launcher (a beacon, button or hotspot) is shown to a user.

• Trigger
  Question Answered

  Triggered when a user answers a question in a Userflow flow — a survey, NPS or rating step. The answer arrives as text, a number, or a list depending on the question type.

• Trigger
  User Created/Updated

  Triggered when a user is created or changed in Userflow.

• Action
  Create/Update Group

  Creates a group (a company or account) in Userflow, or updates it if a group with that ID already exists. Only the attributes you send are changed.

• Action
  Create/Update User

  Creates a user in Userflow, or updates them if a user with that ID already exists. Only the attributes you send are changed. Optionally adds the user to a group.

• Action
  Find Group

  Finds groups (companies or accounts) in Userflow by name. Userflow's API cannot filter on the server, so this reads up to 300 groups and matches them here; leave the name blank to just list them.

• Action
  Find User

  Finds users in Userflow by email or name. Userflow's API cannot filter on the server, so this reads up to 300 users and matches them here; leave both fields blank to just list them.

• Action
  Track Event

  Tracks an event for a user in Userflow, so you can use it to start flows or checklists and to segment users.

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