Connect NetHunt CRM to Botdog

Both apps 46NetHunt CRM 16Botdog 30

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

• Action
  Add blacklist

  Creates a new blacklist (suppression list) in Botdog so leads on it are excluded from campaigns.

• Action
  Add campaign

  Creates a new outreach campaign in Botdog, optionally with a start and end date.

• Action
  Add Contact to a Campaign

  Adds one contact to a Botdog campaign by LinkedIn profile URL, with optional name, title, company, location and custom attributes for message personalization.

• Action
  Add leads to blacklist

  Adds up to 100 LinkedIn profiles to a Botdog blacklist so they are excluded from campaigns. Duplicates are skipped.

• Action
  Add leads to campaign

  Adds up to 100 leads to a Botdog campaign in one call, each identified by LinkedIn profile URL.

• Action
  Add leads to list

  Adds up to 100 LinkedIn profiles to a Botdog lead list. Duplicates are skipped.

• Action
  Add list

  Creates a new lead list in Botdog to hold LinkedIn profiles you want to group together.

• Action
  Add snippet

  Creates a reusable message snippet in Botdog — either a static text template or an LLM prompt — for use in campaign messages.

• Action
  Archive campaign

  Archives a Botdog campaign. It disappears from the active list immediately and finishes archiving in the background.

• Action
  Delete campaign

  Deletes a Botdog campaign. It disappears immediately and is removed in the background.

• Action
  Delete snippet

  Deletes one of your own message snippets in Botdog.

• Action
  Get campaign

  Returns one Botdog campaign by id, with its name, status, owner and schedule.

• Action
  Get campaign sequence

  Returns a campaign's sequence — its steps and the branch conditions between them — as configured in the Botdog editor.

• Action
  Get campaign statistics

  Returns a campaign's performance: invitations and messages sent, acceptances, replies, profile visits and the resulting rates.

• Action
  Get lead

  Returns one lead by id, including profile details, campaign status and the lead's full event history.

• Action
  Get list

  Returns one Botdog lead list by id, with its name and lead count.

• Action
  List campaign leads

  Returns the leads in a Botdog campaign, optionally filtered by their campaign status or whether they replied.

• Action
  List campaigns

  Returns the campaigns on the connected Botdog team, optionally filtered by status or owner.

• Action
  List leads

  Returns leads across the Botdog team, optionally narrowed to a campaign or list and filtered by reply, unread or skipped state.

• Action
  List leads in list

  Returns the leads in a Botdog lead list.

• Action
  List paused campaign activities

  Returns which activity types — profile visits, invitations, messages and so on — are currently paused for a Botdog campaign.

• Action
  List snippets

  Returns the message snippets visible to the connected Botdog user, both personal and team-shared.

• Action
  Pause campaign activities

  Pauses specific activity types — profile visits, invitations, messages — on a campaign without pausing the whole campaign.

• Action
  Remove leads from blacklist

  Removes leads from a Botdog blacklist, identified by lead id or LinkedIn profile URL.

• Action
  Remove leads from list

  Removes leads from a Botdog lead list, identified by lead id or LinkedIn profile URL.

• Action
  Resume campaign activities

  Resumes specific activity types on a Botdog campaign that were paused individually.

• Action
  Stop lead

  Stops a lead's campaign sequence so Botdog sends them nothing further. The lead record is kept.

• Action
  Update campaign

  Updates a Botdog campaign's name or schedule. Fields you leave blank keep their current values.

• Action
  Update lead

  Updates a lead's details in Botdog — name, company, status note and custom fields. Fields you leave blank keep their current values.

• Action
  Update snippet

  Updates a Botdog message snippet — its name, body, prompt, shortcut or archived state. Fields you leave blank keep their current values.

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