Connect YNAB to NetHunt CRM

Both apps 34YNAB 18NetHunt CRM 16

• Trigger
  Category Overspent

  Triggers when a category is overspent and has a negative balance.

• Trigger
  Goal Completed

  Triggers when a goal is completed.

• Trigger
  Low Account Balance

  Triggers when a Checking or Savings account balance drops below a certain amount during a month.

• Trigger
  Low Category Balance

  Triggers when a category balance drops below a certain amount.

• Trigger
  New Account

  Triggers when a new account is created.

• Trigger
  New Category

  Triggers when a new category is created.

• Trigger
  New or Updated Account

  Triggers when a new account is created or an existing account is updated.

• Trigger
  New or Updated Category

  Triggers when a new category is created or an existing category is updated.

• Trigger
  New or Updated Scheduled Transaction

  Triggers when a scheduled transaction is created or updated.

• Trigger
  New or Updated Transaction

  Triggers when a transaction is created or updated.

• Trigger
  New Payee

  Triggers when a new payee is created.

• Trigger
  New Transaction

  Triggers when a new transaction is created.

• Trigger
  Spending in Account

  Triggers when a new outflow transaction is created in an account.

• Trigger
  Spending in Category

  Triggers when a new outflow transaction is assigned to a category.

• Action
  Budget to a Category

  Budgets to a category in the current month.

• Action
  Create Transaction

  Creates a new transaction.

• Action
  Get Current Budget Month

  Returns the current month of the last-used budget, including Age of Money, income, budgeted, activity, and to-be-budgeted amounts.

• Action
  Get Current Month Summary

  Returns the current budget month's summary, including age of money, income, budgeted, activity, and to-be-budgeted amounts.

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