Connect Myphoner to NetHunt CRM

Both apps 41Myphoner 25NetHunt CRM 16

• Trigger
  Archived Lead

  Triggers when a lead is archived (marked 'archive').

• Trigger
  Call Back

  Triggers when a lead is marked for 'call back'.

• Trigger
  Lead updated (instant)

  Fires when a lead's information is updated by an agent (webhook event: lead_updated).

• Trigger
  Lost Lead

  Triggers when a lead is lost (marked 'loser').

• Trigger
  New call (instant)

  Fires when a new call is conducted (webhook event: new_call).

• Trigger
  New call recording (instant)

  Fires when a new call recording becomes available (webhook event: new_recording).

• Trigger
  New comment (instant)

  Fires when a new comment is created for a lead (webhook event: new_comment).

• Trigger
  New lead (instant)

  Fires when a new lead is created in Myphoner (webhook event: lead_created).

• Trigger
  New Winner

  Triggers when a lead is won.

• Trigger
  Text message received (instant)

  Fires when a text message is received from a lead (webhook event: inbound_text).

• Trigger
  Text message sent (instant)

  Fires when a text message is sent to a lead (webhook event: text).

• Action
  Archive a lead

  Archives a lead in Myphoner, optionally recording a comment and archive category, or scheduling the lead to come back for a call later.

• Action
  Create a list

  Creates a new lead list in Myphoner, optionally defining its columns.

• Action
  Create Lead

  Creates a lead in a Myphoner list. The lead's fields are the columns defined on the chosen list.

• Action
  Find Lead

  Searches Myphoner for a lead matching your text and returns the first match, optionally limited to certain lists.

• Action
  Get a lead

  Returns one Myphoner lead by its ID, including every column defined on the lead's list.

• Action
  Get a list

  Returns one Myphoner list by its ID, with its name, lead count and the categories configured for each lead state.

• Action
  List leads

  Returns a page of leads from a Myphoner list, newest-updated first when you ask for that order.

• Action
  List lists

  Returns every lead list in the Myphoner account, with each list's name, ID and lead count.

• Action
  Mark Lead as Loser

  Marks a Myphoner lead as lost, optionally recording a comment and loser category or scheduling it to come back for a call later.

• Action
  Mark Lead as Winner

  Marks a Myphoner lead as won, optionally recording a comment and winner category or scheduling it to come back for a call later.

• Action
  Mark Lead for Call Back

  Schedules a Myphoner lead for a call back, optionally recording a comment and category and setting when the lead should come back.

• Action
  Move a lead to another list

  Moves a Myphoner lead into a different list, optionally releasing it back to the calling queue.

• Action
  Search for Lead

  Searches Myphoner leads for your text and returns every match, optionally limited to certain lists.

• Action
  Update Lead

  Updates a lead in Myphoner. Only the fields you fill in are changed; the lead's fields are the columns defined on its list.

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