Connect LaunchDarkly to NetHunt CRM

Both apps 66LaunchDarkly 50NetHunt CRM 16

• Trigger
  Access Token Event

  Triggers when access token activity happens on your LaunchDarkly account.

• Trigger
  Code Reference Repository Event

  Triggers when code reference repository activity happens on your LaunchDarkly account.

• Trigger
  Flag Event

  Triggers when flag activity happens on your LaunchDarkly account.

• Trigger
  Integration Event

  Triggers when integration activity happens on your LaunchDarkly account.

• Trigger
  Member Event

  Triggers when member activity happens on your LaunchDarkly account.

• Trigger
  Relay Proxy Configuration Event

  Triggers when relay proxy configuration activity happens on your LaunchDarkly account.

• Trigger
  Role Event

  Triggers when role activity happens on your LaunchDarkly account.

• Trigger
  Segment Event

  Triggers when segment activity happens on your LaunchDarkly account.

• Trigger
  Service Token Event

  Triggers when service token activity happens on your LaunchDarkly account.

• Trigger
  Team Event

  Triggers when team activity happens on your LaunchDarkly account.

• Trigger
  User Event

  Triggers when user activity happens on your LaunchDarkly account.

• Action
  Add or Remove User Targets From a Feature Flag

  Adds people to, or removes them from, the individual targeting list for one variation of a feature flag in a chosen environment.

• Action
  Create a feature flag

  Creates a new feature flag in a LaunchDarkly project, either a plain on/off flag or one with your own list of variations.

• Action
  Create a metric

  Creates a metric in a LaunchDarkly project so you can measure the effect of a flag or experiment - a custom event, a click, a page view, or a trace.

• Action
  Create an access token

  Creates a LaunchDarkly API access token with the access level you choose. The full token value is returned only on this call, so save it right away.

• Action
  Create an environment

  Adds a new environment to a LaunchDarkly project, so flags can be configured separately for it. Returns the environment's SDK keys.

• Action
  Create a project

  Creates a new LaunchDarkly project, optionally with its own environments and flag-naming rules.

• Action
  Create a segment

  Creates a segment in one environment of a LaunchDarkly project, so you can target a named group of people with your flags.

• Action
  Delete environment

  Deletes an environment from a LaunchDarkly project, along with all the flag settings it held.

• Action
  Delete feature flag

  Permanently deletes a feature flag from a LaunchDarkly project, in every environment.

• Action
  Delete metric

  Deletes a metric from a LaunchDarkly project.

• Action
  Delete project

  Deletes a LaunchDarkly project and everything inside it - all of its environments, flags and segments.

• Action
  Delete segment

  Deletes a segment from one environment of a LaunchDarkly project.

• Action
  Evaluate a Feature Flag

  Works out which variation of each feature flag a particular person (or other context) would be served in one environment, and why.

• Action
  Get access token

  Returns one LaunchDarkly access token by its id, including its name, role, and when it was last used.

• Action
  Get custom role

  Returns one LaunchDarkly custom role by its key, including its name, description, and policy statements.

• Action
  Get environment

  Returns one environment in a LaunchDarkly project, including its keys, colour, and default flag settings.

• Action
  Get feature flag

  Returns one feature flag in a LaunchDarkly project, including its variations, tags, and per-environment settings.

• Action
  Get metric

  Returns one metric in a LaunchDarkly project, including how it is measured and which events it counts.

• Action
  Get project

  Returns one LaunchDarkly project by its key, including its name, tags, and default settings.

• Action
  Get segment

  Returns one segment in a LaunchDarkly project environment, including its included and excluded contexts and its rules.

• Action
  Get team

  Returns one LaunchDarkly team by its key, including its name, description, and how many members and roles it has.

• Action
  List access tokens

  Returns the access tokens in your LaunchDarkly account.

• Action
  List custom roles

  Returns the custom roles in your LaunchDarkly account.

• Action
  List environments

  Returns the environments in one LaunchDarkly project.

• Action
  List feature flags

  Returns the feature flags in one LaunchDarkly project.

• Action
  List metrics

  Returns the metrics in one LaunchDarkly project.

• Action
  List projects

  Returns the projects in your LaunchDarkly account.

• Action
  List segments

  Returns the segments in one LaunchDarkly project environment.

• Action
  List teams

  Returns the teams in your LaunchDarkly account.

• Action
  List users

  Returns the end users LaunchDarkly has seen in one project environment. Built on the contexts API, which replaced the retired users API.

• Action
  Search contexts

  Searches the contexts LaunchDarkly has seen in one project environment using a filter expression.

• Action
  Toggle a Feature Flag

  Turns a LaunchDarkly feature flag on or off in one environment.

• Action
  Update a Feature Flag With JSON

  Updates a LaunchDarkly feature flag by sending your own semantic patch instructions as JSON, for changes the ready-made actions do not cover.

• Action
  Update custom role

  Updates a LaunchDarkly custom role — its name, description, base permissions, or policy statements. Fields you leave blank are not changed.

• Action
  Update environment

  Updates an environment in a LaunchDarkly project — its name, colour, cache time, or confirmation settings. Fields you leave blank are not changed.

• Action
  Update metric

  Updates a metric in a LaunchDarkly project — its name, description, tags, or unit. Fields you leave blank are not changed.

• Action
  Update project

  Updates a LaunchDarkly project — its name, tags, or default flag settings. Fields you leave blank are not changed.

• Action
  Update segment

  Updates a segment in a LaunchDarkly project environment — its name, description, tags, or the contexts it includes and excludes. Fields you leave blank are not changed.

• Action
  Update team

  Updates a LaunchDarkly team — its name, description, members, or custom roles. Fields you leave blank are not changed.

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