Connect NetHunt CRM to Attio

Both apps 36NetHunt CRM 16Attio 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.

• Trigger
  List Entry Created

  Triggered when a record is added to an Attio list. Attio registers and removes the webhook automatically when the automation is turned on and off.

• Trigger
  List Entry Deleted

  Triggers when a record is removed from a list in Attio, giving you the deleted list entry's ID along with the list and the parent record it pointed at.

• Trigger
  List Entry Updated

  Triggers when a list attribute on an existing Attio list entry is changed, giving you the entry, the list, the parent record and the attribute that changed.

• Trigger
  Record Created

  Triggers when a new record is created in Attio, giving you the new record's ID and the object it belongs to.

• Trigger
  Record Deleted

  Triggers when a record is deleted in Attio, giving you the deleted record's ID and the object it belonged to.

• Trigger
  Record Updated

  Triggers when an attribute on an Attio record changes, giving you the record, the object it belongs to and the attribute that changed.

• Trigger
  Task Created

  Triggers when a new task is created in Attio, giving you the new task's ID and who created it.

• Action
  Create List Entry

  Adds a record to an Attio list as a new list entry and returns the entry.

• Action
  Create Note

  Creates a note on an Attio record and returns the new note.

• Action
  Create or Update List Entry by Parent Record

  Adds a record to an Attio list, or updates its existing entry if it is already on the list.

• Action
  Create or Update Record

  Creates a record in Attio, or updates the existing record that matches on the chosen field.

• Action
  Create Record

  Creates a new record on the chosen Attio object and returns it.

• Action
  Create Storage Location

  Attaches a folder to an Attio record — either a folder stored in Attio or one linked from Dropbox, Box, Google Drive or OneDrive.

• Action
  Create Task

  Creates a task in Attio, optionally linked to a record and assigned to a workspace member.

• Action
  Delete List Entry

  Removes an entry from an Attio list.

• Action
  Find List Entries

  Returns the entries on an Attio list.

• Action
  Find Records

  Searches records on the chosen Attio object and returns the matches.

• Action
  Update List Entry

  Updates the list-specific field values on an existing Attio list entry. Fields you leave blank are left untouched.

• Action
  Update Record

  Updates the field values on an existing Attio record. Fields you leave blank are left untouched.

• Action
  Update Task

  Updates an existing Attio task's due date, done state, linked records or assignee. Anything you leave blank stays as it is. Attio does not allow the task's text to be changed.

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