Connect NetHunt CRM to Meisterplan

Both apps 35NetHunt CRM 16Meisterplan 19

• 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
  Create or Update Actual Time Worked

  Records the hours a resource or role actually worked on a project for a given date, updating the existing entry if one is already there. Returns the stored entry.

• Action
  Create or Update Allocation

  Allocates a resource or role to a project for a date range, updating the existing allocation if one is already there. Returns the allocation with its resulting segments.

• Action
  Create or Update a Project's Tool Link

  Links a Meisterplan project to the matching project in a task management tool, updating the link if one already exists. Returns the stored link.

• Action
  Create or Update Resource Absence

  Records an absence for a resource over a date range, so the time is taken out of their availability. Returns the stored absence.

• Action
  Create or Update Tasks of a Project's Tool Link

  Pushes a task from a linked task management tool onto a Meisterplan project, updating it if the task key is already there.

• Action
  Create Project

  Creates a project in a Meisterplan scenario, including its dates, budgets and custom fields. Returns the new project.

• Action
  Create Resource

  Adds a person to the Meisterplan resource pool, with their role, calendar, cost rate and org placement. Returns the new resource.

• Action
  Create Role

  Creates a role in Meisterplan that resources can be assigned to and projects can be allocated against. Returns the new role.

• Action
  Find a Resource or Role

  Returns the resources and roles whose key, name or email matches the text you supply. Meisterplan has no server-side search on these collections, so the match is made after fetching them.

• Action
  Find a Team, Resource or Role

  Returns the teams, resources and roles whose name, key or email matches the text you supply. Meisterplan has no server-side search on these collections, so the match is made after fetching them.

• Action
  Find Project by Key

  Returns the project in a scenario that carries the project key you supply. Meisterplan has no server-side project search, so the match is made after fetching the scenario's projects.

• Action
  Find Project by Name

  Returns the projects in a scenario whose name contains the text you supply. Meisterplan has no server-side project search, so the match is made after fetching the scenario's projects.

• Action
  Find Resource by Email

  Returns the resource whose email address matches the one you supply. Meisterplan has no server-side resource search, so the match is made after fetching the resource pool.

• Action
  Find Resource by Key

  Returns the resource carrying the resource key you supply. Meisterplan has no server-side resource search, so the match is made after fetching the resource pool.

• Action
  Find Role by Name

  Returns the role carrying the name you supply. Meisterplan has no server-side role search, so the match is made after fetching the roles.

• Action
  Find Task by Key

  Returns the task on a project's tool link that carries the task key you supply. Meisterplan has no server-side task search, so the match is made after fetching the project's tasks.

• Action
  Update Project

  Updates a project in a Meisterplan scenario — its dates, budgets, status and custom fields. Only the values supplied are changed. Returns the updated project.

• Action
  Update Resource

  Updates a person in the Meisterplan resource pool — their name, role, calendar, cost rate and org placement. Only the values supplied are changed. Returns the updated resource.

• Action
  Update Role

  Updates a role in Meisterplan — its name, cost rate and org placement. Only the values supplied are changed. Returns the updated role.

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