Connect Frihet to NetHunt CRM

Both apps 54Frihet 38NetHunt CRM 16

• Trigger
  New Expense

  Fires when a new expense is created. Backed by vendor webhook registration (POST /v1/webhooks, event=expense.created).

• Action
  Add Client

  Create a client. POST /v1/clients

• Action
  Add Deposit

  Create a deposit. POST /v1/deposits

• Action
  Add Expense

  Create an expense. POST /v1/expenses

• Action
  Add Invoice

  Create an invoice. POST /v1/invoices

• Action
  Add Product

  Create a product. POST /v1/products

• Action
  Add Quote

  Create a quote. POST /v1/quotes

• Action
  Add Vendor

  Create a vendor. POST /v1/vendors

• Action
  Apply deposit to invoice

  Apply a deposit balance to an invoice. POST /v1/deposits/{depositId}/apply

• Action
  Delete Client

  Delete a client. DELETE /v1/clients/{clientId}

• Action
  Delete Expense

  Delete an expense. DELETE /v1/expenses/{expenseId}

• Action
  Delete Invoice

  Delete an invoice. DELETE /v1/invoices/{invoiceId}

• Action
  Delete Product

  Delete a product. DELETE /v1/products/{productId}

• Action
  Delete Quote

  Delete a quote. DELETE /v1/quotes/{quoteId}

• Action
  Delete Vendor

  Delete a vendor. DELETE /v1/vendors/{vendorId}

• Action
  Get Client

  Retrieve a client by id. GET /v1/clients/{clientId}

• Action
  Get Deposit

  Retrieve a deposit by id. GET /v1/deposits/{depositId}

• Action
  Get Expense

  Retrieve an expense by id. GET /v1/expenses/{expenseId}

• Action
  Get Invoice

  Retrieve an invoice by id. GET /v1/invoices/{invoiceId}

• Action
  Get Product

  Retrieve a product by id. GET /v1/products/{productId}

• Action
  Get Quote

  Retrieve a quote by id. GET /v1/quotes/{quoteId}

• Action
  Get Vendor

  Retrieve a vendor by id. GET /v1/vendors/{vendorId}

• Action
  List Clients

  List clients. GET /v1/clients

• Action
  List Deposits

  List deposits. GET /v1/deposits

• Action
  List Expenses

  List expenses. GET /v1/expenses

• Action
  List Invoices

  List invoices. GET /v1/invoices

• Action
  List Products

  List products. GET /v1/products

• Action
  List Quotes

  List quotes. GET /v1/quotes

• Action
  List Vendors

  List vendors. GET /v1/vendors

• Action
  Mark invoice as paid

  Mark an invoice as paid. POST /v1/invoices/{invoiceId}/paid

• Action
  Send Invoice

  Send invoice by email to the client. POST /v1/invoices/{invoiceId}/send

• Action
  Send Quote

  Send quote by email to the client. POST /v1/quotes/{quoteId}/send

• Action
  Update Client

  Partial update a client. PATCH /v1/clients/{clientId}

• Action
  Update Expense

  Partial update an expense. PATCH /v1/expenses/{expenseId}

• Action
  Update Invoice

  Partial update an invoice. PATCH /v1/invoices/{invoiceId}

• Action
  Update Product

  Partial update a product. PATCH /v1/products/{productId}

• Action
  Update Quote

  Partial update a quote. PATCH /v1/quotes/{quoteId}

• Action
  Update Vendor

  Partial update a vendor. PATCH /v1/vendors/{vendorId}

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