Connect Assembly.com to NetHunt CRM

Both apps 98Assembly.com 82NetHunt CRM 16

• Trigger
  Client Activated

  Triggers when a client authenticates in the Assembly for the first time

• Trigger
  Client Created

  Triggers when a new client is created.

• Trigger
  Client Updated

  High-frequency trigger for each client user update.

• Trigger
  Company Created

  Triggers when a company gets created in the Assembly for the first time

• Trigger
  Company Custom Fields Updated

  Triggers only when a company has updates to custom fields.

• Trigger
  Contract Requested

  Triggers when a contract is assigned to a client.

• Trigger
  Contract Signed

  Triggers when a contract is signed.

• Trigger
  File Created

  Triggers when a file gets created within a file channel

• Trigger
  File Updated

  Triggers when a file has been updated within a file channel

• Trigger
  Folder Created

  Triggers when a folder gets created within a file channel

• Trigger
  Folder Deleted

  Triggers when a folder gets deleted within a file channel

• Trigger
  Folder Updated

  Triggers when a folder gets updated within a file channel

• Trigger
  Form Response Completed

  Triggers when a form response has been completed by a recipient

• Trigger
  Internal User Created

  Triggers when a new internal user is created.

• Trigger
  Invoice Created

  Triggers when an invoice is created

• Trigger
  Invoice Deleted

  Triggers when an invoice is deleted

• Trigger
  Invoice Paid

  Triggers when an invoice is paid

• Trigger
  Invoice Sent

  Triggers when an invoice is sent

• Trigger
  Invoice Updated

  Triggers when an invoice is updated

• Trigger
  Invoice Voided

  Triggers when an invoice is voided

• Trigger
  Link Created

  Triggers when a link gets created within a file channel

• Trigger
  Link Updated

  Triggers when a link gets updated within a file channel

• Trigger
  List Clients

  Lists the clients.

• Trigger
  List Companies

  Lists the companies.

• Trigger
  List Form Responses

  List Form Responses for a specific form

• Trigger
  List Invoice Templates

  Lists the invoice templates.

• Trigger
  List Message Channels

  Lists the message channels.

• Trigger
  List Messages

  Lists messages in a channel

• Trigger
  List Notes

  Lists notes in a workspace.

• Trigger
  List Payments

  Lists the payments.

• Trigger
  List Prices

  Lists the prices.

• Trigger
  List Products

  Lists the products.

• Trigger
  List Subscriptions

  Lists the subscriptions.

• Trigger
  List Subscription Templates

  Lists the subscription templates.

• Trigger
  List Task Comments

  Lists task comments in a workspace.

• Trigger
  List Tasks

  Lists tasks in a workspace.

• Trigger
  List Task Templates

  Lists task templates in a workspace.

• Trigger
  Message Channel Created

  Triggers when a new message channel is created.

• Trigger
  Message Channel Deleted

  Triggers when a message channel is deleted.

• Trigger
  Message Sent

  Triggers when a message gets sent in any channels belonging to the portal

• Trigger
  Note Created

  Triggers when a new note is created.

• Trigger
  Note Updated

  Triggers when a note is updated.

• Trigger
  Notification Created

  Triggers when a new notification is created.

• Trigger
  Payment Failed

  Triggers when a payment is failed for an invoice

• Trigger
  Payment Succeeded

  Triggers when a payment is successful for an invoice

• Trigger
  Price Created

  Triggers when a price is created

• Trigger
  Product Created

  Triggers when a product is created

• Trigger
  Product Updated

  Triggers when a product is updated

• Trigger
  Subscription Canceled

  Triggers when an subscription is canceled

• Trigger
  Subscription Created

  Triggers when an subscription is created

• Trigger
  Task Archived

  Triggers when a task gets archived in your workspace.

• Trigger
  Task Completed

  Triggers when a task gets completed in your workspace.

• Trigger
  Task Created

  Triggers when a task gets created in your workspace.

• Trigger
  Task Deleted

  Triggers when a task gets deleted in your workspace.

• Trigger
  Task Updated

  Triggers when a task gets updated in your workspace.

• Action
  Create Client

  Creates a new client.

• Action
  Create Company

  Creates a new company.

• Action
  Create File

  Creates a file in a specified files channel.

• Action
  Create Folder

  Creates a folder in a specified file channel.

• Action
  Create Link

  Creates a link in a specified files channel.

• Action
  Create Message Channel

  Creates a new message channel.

• Action
  Create Note

  Creates a new note.

• Action
  Find a Client

  Search for a client by ID, email, or company.

• Action
  Find a Company

  Search for a company by ID or name.

• Action
  Find a File

  Search for a file by ID.

• Action
  Find a Form

  Search for a Form by ID.

• Action
  Find a Message Channel

  Search for a message channel by ID or by filters

• Action
  Find an Internal User

  Search for an internal user by ID.

• Action
  Find an Invoice

  Search for an invoice by ID.

• Action
  Find a Note

  Search for a note by ID or by filters

• Action
  Find a Price

  Search for a Price by ID.

• Action
  Find a Product

  Search for a Product by ID.

• Action
  Find a Subscription

  Search for a Subscription by ID.

• Action
  Find a Task

  Search for a task by ID or by filters

• Action
  Find a Task Comment

  Search for a task comment by ID

• Action
  Find a Task Template

  Search for a task template by ID or by filters

• Action
  Request Form Responses

  Ask clients to fill out a form.

• Action
  Send Message

  Create and send a message to a designated message channel.

• Action
  Update Client

  Update a client

• Action
  Update Company

  Update the name of a company

• Action
  Update Internal User

  Update an internal user

• Action
  Update Note

  Update the title and content of a note.

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