Connect NetHunt CRM to Productboard

Both apps 32NetHunt CRM 16Productboard 16

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

• Trigger
  New Feature

  Triggered when a new feature is created in Productboard.

• Trigger
  New Note

  Triggered when a new note (a piece of customer feedback) is created in Productboard.

• Trigger
  Updated Feature

  Triggered when a feature is created or changed in Productboard.

• Trigger
  Updated Note

  Triggered when a note (a piece of customer feedback) is created or changed in Productboard.

• Action
  Create Company

  Creates a company record in Productboard so customer feedback and insights can be attributed to it. Returns the new company's ID and a link to open it in Productboard.

• Action
  Create Feature

  Creates a feature in Productboard under a product or component you choose. Optionally sets the description, owner and status. Returns the new feature's ID and a link to open it in Productboard.

• Action
  Create Note

  Creates a note (a piece of customer feedback) in Productboard. Optionally attributes it to a company or customer, links it to a feature, and applies existing tags. Returns the new note's ID and a link to open it in Productboard.

• Action
  Find Note

  Looks up a single note (customer feedback) in Productboard. Narrows the list by owner, created date and processed/archived state, then matches the text you give against the note's title and body. Returns the first match, or found=false.

• Action
  Get Company

  Returns one company from Productboard by its ID, including its name, domain, description, owner and any custom fields set up in your workspace.

• Action
  Get Feature by ID

  Returns one feature from Productboard by its ID, including its name, description, owner, status and any custom fields set up in your workspace.

• Action
  List Components

  Returns the components in your Productboard workspace — the folders that features live under. Use a component's ID as the parent when creating a feature.

• Action
  List Members

  Returns the people who have access to your Productboard workspace, with their email address and role. Optionally search by name or email and filter by role.

• Action
  List Note Relationships

  Returns everything a Productboard note is linked to — the customer or company it came from and the features it has been connected to.

• Action
  List Products

  Returns the products in your Productboard workspace — the top level of the product hierarchy. Use a product's ID as the parent when creating a feature or component.

• Action
  List Releases

  Returns the releases in your Productboard workspace — the buckets features are grouped into for delivery — with their status and dates.

• Action
  Update Note

  Changes an existing note in Productboard. Only the values you fill in are sent, so anything left empty keeps its current value.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.