Connect NetHunt CRM to ConfigCat

Both apps 44NetHunt CRM 16ConfigCat 28

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

• Action
  Add Config

  Create a new config within a product. POST /v1/products/{productId}/configs

• Action
  Add Flag

  Create a new feature flag or setting within a config. POST /v1/configs/{configId}/settings

• Action
  Add Segment

  Create a new segment within a product. POST /v1/products/{productId}/segments

• Action
  Add Tag

  Create a new tag within a product. POST /v1/products/{productId}/tags

• Action
  Delete Config

  Delete a config. DELETE /v1/configs/{configId}

• Action
  Delete Flag

  Delete a feature flag or setting. DELETE /v1/settings/{settingId}

• Action
  Delete Segment

  Delete a segment. DELETE /v1/segments/{segmentId}

• Action
  Delete Tag

  Delete a tag. DELETE /v1/tags/{tagId}

• Action
  Get Config

  Get a single config by id. GET /v1/configs/{configId}

• Action
  Get Environment

  Get a single environment by id. GET /v1/environments/{environmentId}

• Action
  Get Flag

  Get a single feature flag or setting by id. GET /v1/settings/{settingId}

• Action
  Get Flag value

  Get the current served value of a feature flag or setting in an environment. GET /v1/settings/{settingKeyOrId}/value

• Action
  Get Product

  Get a single product by id. GET /v1/products/{productId}

• Action
  Get Segment

  Get a single segment by id. GET /v1/segments/{segmentId}

• Action
  Get Tag

  Get a single tag by id. GET /v1/tags/{tagId}

• Action
  List Configs

  List all configs (SDK config bundles) within a product. GET /v1/products/{productId}/configs

• Action
  List Environments

  List all environments within a product. GET /v1/products/{productId}/environments

• Action
  List Flags

  List all feature flags and settings within a config. GET /v1/configs/{configId}/settings

• Action
  List Organizations

  List all organizations the caller has access to. GET /v1/organizations

• Action
  List Products

  List all products the caller has access to. GET /v1/products

• Action
  List Segments

  List all segments within a product. GET /v1/products/{productId}/segments

• Action
  List Tags

  List all tags within a product. GET /v1/products/{productId}/tags

• Action
  Update Config

  Update a config's name/description/order. PUT /v1/configs/{configId}

• Action
  Update Environment

  Update an environment's name/color/description. PUT /v1/environments/{environmentId}

• Action
  Update Flag

  Update a feature flag or setting's metadata (name, hint, tags). PATCH /v1/settings/{settingId}

• Action
  Update Flag value

  Update (turn on/off, change served value or targeting) a feature flag or setting's value in an environment. PATCH /v1/settings/{settingKeyOrId}/value

• Action
  Update Segment

  Update a segment's name/rules. PUT /v1/segments/{segmentId}

• Action
  Update Tag

  Update a tag's name/color. PUT /v1/tags/{tagId}

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