Connect Timing to NetHunt CRM

Both apps 39Timing 23NetHunt CRM 16

• Trigger
  New Project

  Triggered when a new project is created in Timing.

• Trigger
  New Team

  Triggered when you are added to a new team in Timing.

• Trigger
  New Time Entry

  Triggered when a new time entry is logged in Timing.

• Trigger
  New Timer Started and Running

  Triggered when a new timer is started and is still running in Timing.

• Action
  Batch Update Time Entries

  Updates several Timing time entries at once — moves them to a project, retitles them, sets notes, billing status or custom fields. Anything left blank is left untouched on the entries.

• Action
  Create Project

  Creates a new project in Timing, optionally under a parent project, and returns the created project.

• Action
  Create Time Entry

  Logs a finished block of work in Timing between a start and end time, optionally against a project, and returns the created time entry.

• Action
  Delete Project

  Deletes a project in Timing, along with all of its child projects.

• Action
  Delete Time Entry

  Deletes a time entry in Timing.

• Action
  Find Project

  Searches your Timing projects by title and returns the first match, plus the full list of matches.

• Action
  Find Team

  Finds a team you belong to in Timing by its name and returns the first match, plus every team whose name matched.

• Action
  Get Activity Hierarchy

  Returns a readable breakdown of what you worked on in Timing over a date range, as tab-indented text grouped by project and app with durations.

• Action
  List Projects

  Returns the projects you can see in Timing, optionally filtered by title, team, or hiding archived ones.

• Action
  List Teams

  Returns all the Timing teams you are a member of.

• Action
  List Time Entries

  Returns your Timing time entries, optionally narrowed by date range, project, team member, search text or billing status.

• Action
  Show Latest Time Entry

  Returns your most recent time entry in Timing.

• Action
  Show Project

  Returns a single Timing project with its colour, notes, billing default, parent and child projects.

• Action
  Show Running Timer

  Returns the timer that is currently running in Timing. Errors with a not-found if no timer is running.

• Action
  Show Time Entry

  Returns a single Timing time entry with its times, duration, project, notes and billing status.

• Action
  Start Timer

  Starts a running timer in Timing, stopping any timer that is already running, and returns the new entry.

• Action
  Stop Timer

  Stops the timer that is currently running in Timing and returns the finished time entry.

• Action
  Update Project

  Updates a Timing project's name, colour, notes, archive state or billing default. Anything left blank keeps its current value.

• Action
  Update Time Entry

  Updates a Timing time entry — its times, project, title, notes or billing status. Anything left blank keeps its current value.

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