Connect Streak to NetHunt CRM

Both apps 49Streak 33NetHunt CRM 16

• Trigger
  New Box

  Triggered when a new box is added to the specified pipeline (polling).

• Trigger
  New email thread

  Triggered when a new email thread is added to the specified box.

• Trigger
  New event

  Triggered when a new event occurs within any pipeline.

• Trigger
  New event in box

  Triggered when a new event occurs within the specified box.

• Trigger
  New event in pipeline

  Triggered when a new event occurs within the specified pipeline.

• Trigger
  New file

  Triggered when a new file is added to the specified box.

• Trigger
  New Pipeline

  Triggered when a new pipeline is added (polling).

• Trigger
  New snippet

  Triggered when a new snippet is added.

• Trigger
  New Stage

  Triggered when a new stage is added to the specified pipeline (polling).

• Trigger
  New Task in Box

  Triggered when a new task is added to the specified box (polling).

• Trigger
  New task in pipeline

  Fires for each new task created in the selected Streak pipeline. Polls every box in the pipeline and emits each task once, identified by its task key.

• Trigger
  Task complete

  Fires for each task marked complete in the selected Streak pipeline. Polls every box in the pipeline, keeps the tasks whose status is DONE, and emits each one once, identified by its task key.

• Action
  Create Box

  Adds a new box to the specified pipeline.

• Action
  Create Comment

  Adds a new comment to the specified box.

• Action
  Create Pipeline

  Creates a new pipeline.

• Action
  Create Stage

  Adds a new stage to the specified pipeline.

• Action
  Create Task

  Adds a new task to the specified box.

• Action
  Delete Box

  Deletes a box by its key.

• Action
  Delete Stage

  Deletes a stage from the specified pipeline.

• Action
  Delete Task

  Deletes a task by its key.

• Action
  Get Box

  Gets a single box by its key.

• Action
  Get Current User

  Returns the user associated with the API key.

• Action
  Get Pipeline

  Gets a single pipeline by its key.

• Action
  List Boxes in Pipeline

  Lists all boxes in the specified pipeline.

• Action
  List Fields

  Lists all fields in the specified pipeline.

• Action
  List Pipelines

  Lists all pipelines the user has access to.

• Action
  List Stages

  Lists all stages in the specified pipeline.

• Action
  List Tasks in Box

  Lists all tasks in the specified box.

• Action
  Move Box to Stage

  Moves a box to a stage in the specified pipeline.

• Action
  Search

  Searches boxes, contacts, and organizations across Streak.

• Action
  Update Box

  Updates a box's name, notes, or stage.

• Action
  Update Box Field Value

  Sets the value of a custom field on a box.

• Action
  Update Task

  Updates a task's text, due date, or completion status.

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