Connect Clockify to NetHunt CRM

Both apps 47Clockify 31NetHunt CRM 16

• Trigger
  New Client

  Triggers when a new client is added to a workspace.

• Trigger
  New Project

  Triggers when a new project is added to a workspace.

• Trigger
  New Tag

  Triggers when a new tag is added to a workspace.

• Trigger
  New Task

  Triggers when a new task is added to a project on a specified workspace.

• Trigger
  New Time Entry

  Triggers when a new time entry is added.

• Trigger
  New Timer Started

  Triggers when a new entry is started and running.

• Trigger
  New Workspace

  Triggers when a new workspace is created.

• Action
  Create Client

  Creates a client on a specified workspace.

• Action
  Create Project

  Creates a project on a specified workspace.

• Action
  Create Tag

  Creates a tag on a specified workspace.

• Action
  Create Task

  Creates a task on a specified project.

• Action
  Create Time Entry

  Creates a new time entry on a specified workspace.

• Action
  Delete Client

  Delete a client from a workspace. DELETE /v1/workspaces/{workspaceId}/clients/{id}

• Action
  Delete Project

  Delete a project from a workspace. DELETE /v1/workspaces/{workspaceId}/projects/{projectId}

• Action
  Delete Tag

  Delete a tag from a workspace. DELETE /v1/workspaces/{workspaceId}/tags/{id}

• Action
  Delete Task

  Delete a task from a project. DELETE /v1/workspaces/{workspaceId}/projects/{projectId}/tasks/{taskId}

• Action
  Delete Time Entry

  Delete a time entry from a workspace. DELETE /v1/workspaces/{workspaceId}/time-entries/{id}

• Action
  Find Client

  Finds a client by name on a specified workspace.

• Action
  Find Project

  Finds a project by name on a specified workspace.

• Action
  Find Running Timer

  Finds a currently running time entry on a specified workspace.

• Action
  Find Tag

  Finds a tag on a specified workspace.

• Action
  Find Task

  Finds a task by name on a specified project and workspace.

• Action
  Find Time Entry

  Finds a time entry by description, start datetime or end datetime.

• Action
  List Workspaces

  List all workspaces the authenticated user belongs to. GET /v1/workspaces

• Action
  Start Timer

  Starts a new time entry.

• Action
  Stop Timer

  Stops currently running time entry on a specified workspace.

• Action
  Update Client

  Update a client's name/note/archived status. PUT /v1/workspaces/{workspaceId}/clients/{id}

• Action
  Update Project

  Update a project's name/color/client/billable status/dates. PUT /v1/workspaces/{workspaceId}/projects/{projectId}

• Action
  Update Tag

  Update a tag's name/archived status on a workspace. PUT /v1/workspaces/{workspaceId}/tags/{id}

• Action
  Update Task

  Update a task's name/status/assignee/estimate on a project. PUT /v1/workspaces/{workspaceId}/projects/{projectId}/tasks/{taskId}

• Action
  Update Time Entry

  Update a time entry's start/end/description/project/task/billable/tags on a workspace. PUT /v1/workspaces/{workspaceId}/time-entries/{id}

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