Connect NetHunt CRM to Notion

Both apps 44NetHunt CRM 16Notion 28

• 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
  New Comment

  Triggers when a new comment is created in your Notion workspace. You can filter by database or specific page.

• Trigger
  New Data Source Item

  Triggers when a new item is created in a data source.

• Trigger
  Updated Content in Data Source Item

  Triggers when the content in a data source item is updated.

• Trigger
  Updated Content in Page

  Triggers when the content in a page is updated.

• Trigger
  Updated Properties in Data Source Item

  Triggers when one or more properties of a data source item are updated.

• Action
  Add Block to Page

  Adds a new content block to an existing Notion page. Supports various block types including paragraphs, headings, lists, to-dos, callouts, code blocks, and more.

• Action
  Add Comment

  Adds a new comment to a Page.

• Action
  Add Content to Page

  Adds Content to a Page.

• Action
  Archive Data Source Item

  Soft deletes an item in a data source.

• Action
  Create Data Source Item

  Creates an item in a data source.

• Action
  Create Page

  Creates a Page inside a parent page

• Action
  Find Data Source Items

  Searches for items in a data source by its properties.

• Action
  Find Page (By Title)

  Searches for a page by title.

• Action
  Get Block

  Retrieves a block by ID.

• Action
  Get Block Children

  Retrieves child blocks of a parent block or page with support for pagination.

• Action
  Get Page

  Retrieves a specific page or data source item from Notion using its ID.

• Action
  Get Page and Children

  Retrieves a page by its ID and all of its block children.

• Action
  Get Page Comments

  Retrieves comments from a Page.

• Action
  Get Page Property

  Retrieves a specific property value from a Notion page.

• Action
  Get User Details

  Retrieves user information by ID.

• Action
  Query Data Source (Advanced)

  Query a Notion data source with advanced filtering and sorting using JSON. Supports complex logic like AND/OR conditions, multiple sorts, and all Notion filter types.

• Action
  Restore Data Source Item

  Restores a data source item which was previously archived.

• Action
  Retrieve Database

  This action retrieves a database in Notion using the ID of the database.

• Action
  Update Database

  Updates a Notion database attributes including title, parent location, inline display, icon, archive status, and lock status.

• Action
  Update Data Source Item

  Updates a data source item.

• Action
  Update Data Source Schema

  Updates a Notion data source schema including properties and title. Allows adding, modifying, or removing data source properties to change the schema.

• Action
  Upload File to Data Source Item

  Uploads a file to a files property in a data source item.

• Action
  Upload File to Page or Block

  Uploads a file to a page or block in Notion.

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