Connect Ninety to NetHunt CRM

Both apps 41Ninety 25NetHunt CRM 16

• Trigger
  New Issue Created

  Triggered when a new issue is created in Ninety, optionally only on one team or only short-term vs long-term issues.

• Trigger
  New Measurable

  Triggered when a new measurable (KPI) is added to your Ninety scorecard, optionally only those tracked over a given period like weekly or monthly.

• Trigger
  New Team

  Triggered when a new team is created in your Ninety company.

• Trigger
  To-Do Created, Updated, or Deleted

  Triggered when a to-do is created or changed in Ninety — including being completed or archived — optionally only on one team or only personal to-dos. Ninety's API does not report hard deletions, so a removed to-do simply stops appearing rather than firing this trigger.

• Action
  Create Issue

  Creates an issue on a Ninety team's issues list.

• Action
  Create Milestone

  Creates a milestone on a Ninety rock, with a title and due date.

• Action
  Create Rock

  Creates a rock (a quarterly goal) for a Ninety team, with a due date, status and level.

• Action
  Create To-Do

  Creates a to-do on a Ninety team, with a due date and optional description.

• Action
  Delete Issue

  Deletes an existing Issue in Ninety by its ID.

• Action
  Delete Measurable Note

  Deletes the note on a Measurable for one scorecard period.

• Action
  Delete Measurable Score

  Deletes the score on a Measurable for one scorecard period.

• Action
  Delete Rock

  Deletes a Rock in Ninety by its ID. Returns the deleted Rock's ID along with the status Ninety returned.

• Action
  Delete To-Do

  Deletes a to-do in Ninety by its ID. Use it to remove a to-do that was created by mistake or is no longer needed.

• Action
  Find Issue

  Searches Ninety for issues matching the words you provide, optionally narrowed to one team or to short-term vs long-term issues. Returns the matching issues.

• Action
  Find Measurable

  Searches Ninety's scorecard for measurables (KPIs) matching the words you provide, optionally limited to a tracking period like weekly or monthly. Returns the matching measurables.

• Action
  Find Milestone

  Searches Ninety for milestones by title. Ninety carries milestones on their rocks, so this reads the rocks (optionally just one team's) and returns the milestones whose title matches, optionally limited to a single rock.

• Action
  Find Rock

  Searches Ninety for rocks (quarterly goals) matching the words you provide, optionally narrowed to one team or one status. Returns the matching rocks.

• Action
  Find Team

  Returns the teams in your Ninety company, optionally only those whose name contains the words you provide. Use it to get the team ID other Ninety actions need.

• Action
  Find To-Do

  Searches Ninety for to-dos matching the words you provide, optionally narrowed to one team, to personal to-dos, or to finished vs open ones. Returns the matching to-dos.

• Action
  Update Issue

  Changes an existing issue in Ninety — its title, detail, team, priority, short-term/long-term setting, or whether it is solved. Fields you leave blank are left as they are.

• Action
  Update Measurable Note

  Saves the note on a Ninety scorecard measurable for one period, replacing any note already there.

• Action
  Update Measurable Score

  Records the score on a Ninety scorecard measurable for one period, replacing any score already there.

• Action
  Update Milestone

  Changes an existing milestone in Ninety — its title, detail, due date, owner, or whether it is finished. Fields you leave blank are left as they are.

• Action
  Update Rock

  Changes an existing rock (quarterly goal) in Ninety — its title, detail, status, owner, team, quarter, due date, or whether it is archived. Fields you leave blank are left as they are.

• Action
  Update To-Do

  Changes an existing to-do in Ninety — its title, detail, due date, owner, team, repeat setting, or whether it is done or archived. Fields you leave blank are left as they are.

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