Connect NetHunt CRM to TaxJar

Both apps 36NetHunt CRM 16TaxJar 20

• 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
  Calculate Sales Tax for an Order

  Works out the sales tax due on an order from the ship-from and ship-to addresses, the order amount and its line items.

• Action
  Create a Customer

  Creates a customer in TaxJar with their exemption type and the regions the exemption applies to.

• Action
  Create an Order Transaction

  Records a completed order in TaxJar so it counts towards your sales tax reporting.

• Action
  Create a Refund Transaction

  Records a refund against an existing order in TaxJar so your sales tax reporting stays accurate.

• Action
  Get Two-Letter ISO Code for Region

  Looks up the two-letter code for a state, province or country by name, using TaxJar's own list of regions.

• Action
  List Categories

  Returns TaxJar's product categories and the tax code to use for each one.

• Action
  List Customers

  Returns the IDs of every customer in your TaxJar account.

• Action
  List Nexus Regions

  Returns the states, provinces and countries where your TaxJar account has nexus and must collect tax.

• Action
  List Orders

  Returns the IDs of the orders recorded in TaxJar, optionally limited to a date or date range.

• Action
  List Refunds

  Returns the IDs of the refunds recorded in TaxJar, optionally limited to a date or date range.

• Action
  Rates for Location

  Returns the sales tax rates that apply at a location, broken down by state, county and city.

• Action
  Show a Customer

  Returns one customer from TaxJar, including their exemption type and exempt regions.

• Action
  Show Order

  Returns one order recorded in TaxJar, including its addresses, totals and line items.

• Action
  Show Refund

  Returns one refund recorded in TaxJar, including the order it applies to and the amounts refunded.

• Action
  Summarize Tax Rates for All Regions

  Returns the minimum and average sales tax rate for every state, province and country TaxJar covers.

• Action
  Update a Customer

  Updates a customer in TaxJar. Only the fields you supply are changed.

• Action
  Update an Order Transaction

  Updates an order already recorded in TaxJar. Only the fields you supply are changed.

• Action
  Update a Refund Transaction

  Updates a refund already recorded in TaxJar. Only the fields you supply are changed.

• Action
  Validate an Address

  Checks a US address and returns TaxJar's corrected version of it, so tax is worked out on a clean address.

• Action
  Validate a VAT Number

  Checks whether a VAT number is valid and returns the business name and address registered against it.

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