Connect Metaview to NetHunt CRM

Both apps 48Metaview 32NetHunt CRM 16

• Trigger
  New Conversation

  Triggers when a new conversation is available in Metaview.

• Action
  Build chart

  Creates a visual chart from conversation data with optional filtering, grouping, and timezone adjustment.

• Action
  Check enrichment status

  Returns enrichment status and usage metrics for candidate data, with options to scope by person or enrichment type.

• Action
  Create AI field

  Creates a new AI-powered field that analyzes conversations to answer a custom question, with configurable value type.

• Action
  Create report

  Builds a report from conversations with filtering, metrics, grouping, and custom field inclusion.

• Action
  Fetch candidates

  Looks up candidate information by ID, LinkedIn URL, email, or phone number in bulk.

• Action
  Find candidate's sequences

  Finds which outreach sequences a candidate is enrolled in using their ID, LinkedIn URL, email, or phone.

• Action
  Get note template

  Returns a note generation template by ID for use in automating note creation.

• Action
  Get search details

  Retrieves configuration and results for a sourcing search by ID.

• Action
  Get sourcing analytics

  Returns sourcing analytics and metrics grouped by user, search, or date range with filtering options.

• Action
  Get sourcing messages

  Lists outreach messages sent in a sourcing search with pagination support.

• Action
  Get User Context

  Returns information about the connected user account and available features.

• Action
  Give sourcing feedback

  Submits feedback on candidates from a sourcing search, optionally linking to the search that sourced them.

• Action
  Group conversations

  Groups recorded conversations by a field (like recruiter, stage, or outcome) and returns counts and metrics per group.

• Action
  List application reviews

  Returns a list of application reviews, optionally filtering by name or showing only active ones.

• Action
  List ATS jobs

  Returns ATS job postings, optionally filtered by job title.

• Action
  List ATS stages

  Returns hiring pipeline stages for a job, or workspace-level stages if no job is specified.

• Action
  List available fields

  Returns available data fields for reports, optionally filtered by name.

• Action
  List candidates in sequence

  Returns candidates enrolled in a sequence, with optional enrollment status and per-step delivery details.

• Action
  List field values

  Returns distinct values for a field across conversations, useful for building filters or dropdowns.

• Action
  List mailboxes

  Returns email mailboxes available in this Metaview workspace.

• Action
  List note template folders

  Returns folders of note templates organized in the workspace.

• Action
  List note templates

  Returns note templates available in the workspace, optionally filtered by name or with full section details.

• Action
  List sequences

  Returns candidate sequences, optionally filtered by name, creator, or status; includes full configuration if requested.

• Action
  List sourcing candidates

  Returns candidates from a specified sourcing search with optional filtering by pack, feedback status, and detail level.

• Action
  List sourcing searches

  Returns all sourcing searches with optional pagination.

• Action
  Manage candidate sequence

  Adds, pauses, resumes, cancels, removes, or updates candidate enrollments in a recruitment sequence.

• Action
  Manage note template

  Creates, updates, or deletes call note templates with customizable sections for structured note-taking.

• Action
  Manage sequence

  Creates, updates, duplicates, or deletes recruitment sequences.

• Action
  Search conversations

  Searches call conversations with optional filtering, sorting, and field selection.

• Action
  Search reports

  Searches reports by name, category, or ID with optional full configuration details.

• Action
  Send sourcing message

  Starts or continues a sourcing or research search with a message to the AI agent.

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