Connect NetHunt CRM to Teamup Calendar

Both apps 33NetHunt CRM 16Teamup Calendar 17

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

• Trigger
  Event Cancelled

  Triggers when an event is cancelled (deleted) on your Teamup calendar. Polls the calendar's change feed and emits each newly deleted event.

• Trigger
  Event Ended

  Triggers when an event on your Teamup calendar has ended. Polls the last day of events and emits each one whose end time has passed.

• Trigger
  Event Start

  Triggers when an event on your Teamup calendar has started. Polls the last day of events and emits each one whose start time has passed.

• Trigger
  New Event

  Triggers when a new event is added to your Teamup calendar.

• Trigger
  New Event Matching Search

  Triggers when a new event matching your search keywords appears on your Teamup calendar.

• Trigger
  New or Updated Event

  Triggers when an event is added or changed on your Teamup calendar.

• Action
  Add Comment

  Posts a comment on an event in your Teamup calendar. Returns the created comment, including its id and creation time.

• Action
  Add Signup

  Signs a person up for an event on your Teamup calendar. Returns the created signup, including its id and creation time.

• Action
  Create Event

  Creates a new event on your Teamup calendar, including any custom event fields defined on the calendar. Returns the created event.

• Action
  Delete Event

  Deletes an event from your Teamup calendar. Returns an undo token for the deletion.

• Action
  Find Event Matching Remote ID

  Finds the event on your Teamup calendar carrying a given remote id. Searches the supplied date range and returns the matching event.

• Action
  Find Events

  Searches your Teamup calendar for events matching a keyword within a date range. Returns the matching events.

• Action
  Get Event

  Returns a single event from your Teamup calendar, including its custom field values, change history and reminders.

• Action
  Get Sub-Calendar

  Returns a single sub-calendar from your Teamup calendar with all its details.

• Action
  List Events

  Returns the events on your Teamup calendar for a date range, optionally limited to selected sub-calendars.

• Action
  List Sub-Calendars

  Returns the sub-calendars on your Teamup calendar.

• Action
  Update Event

  Updates an existing event on your Teamup calendar, including any custom event fields defined on the calendar. Returns the updated event.

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