Connect NetHunt CRM to Woodpecker.co

Both apps 41NetHunt CRM 16Woodpecker.co 25

• 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
  Campaign Completed

  Triggers when a Woodpecker campaign status changes to COMPLETED.

• Trigger
  Email Opened

  Triggers when a prospect opens your email.

• Trigger
  Email Sent

  Triggers when Woodpecker sends an email to prospect from campaign.

• Trigger
  Follow-Up After Autoreply

  Triggers when you set a date for resuming follow-ups after you got an autoreply from a prospect.

• Trigger
  Link Clicked

  Triggers when a prospect clicks on a link in your email.

• Trigger
  Manual Task Created

  Triggers when a manual task of any type is created.

• Trigger
  Manual Task Done

  Triggers when a manual task is marked as done.

• Trigger
  Manual Task Ignored

  Triggers when a manual task is marked as ignored.

• Trigger
  Prospect Autoreplied

  Triggers when you get an autoresponder from a prospect, or when you manually mark a prospect as AUTOREPLIED.

• Trigger
  Prospect Blacklisted

  Triggers when a prospect status is changed to BLACKLISTED manually or when prospect unsubscribes from Woodpecker.

• Trigger
  Prospect Bounced

  Triggers when a prospect’s email address bounces your message and the prospect status gets changed to BOUNCED in Woodpecker.

• Trigger
  Prospect Interested

  Triggers when a prospect is marked as INTERESTED.

• Trigger
  Prospect Invalid

  Triggers when a prospect’s email address doesn't exist on an external server. This check happens when Woodpecker tries to send an email to this prospect. Status is changed to INVALID in Woodpecker.

• Trigger
  Prospect Maybe Later

  Triggers when a prospect's interest level is marked as MAYBE LATER.

• Trigger
  Prospect Nonresponsive

  Triggers when a prospect's status is changed to NONRESPONSIVE

• Trigger
  Prospect Not Interested

  Triggers when a prospect is marked as NOT INTERESTED.

• Trigger
  Prospect Opt Out

  Triggers when prospect unsubscribes from your emails or is marked as OPT-OUT manually.

• Trigger
  Prospect Replied

  Triggers when a prospect replies to your email or is manually marked as REPLIED in Woodpecker.

• Trigger
  Prospect Saved

  Triggers when a Woodpecker prospect is created or updated.

• Trigger
  Secondary Reply

  Triggers when a secondary reply is found by Woodpecker.

• Action
  Blacklist Domain

  Add a domain to a blacklist. It will automatically block ongoing and future sending to all prospects within a given domain.

• Action
  Create/Update Prospect

  Adds a new prospect or Updates existing prospect in the list of Prospects.

• Action
  Create/Update Prospect in Campaign

  Adds a new prospect or updates existing prospect's data in a campaign of choice.

• Action
  Find Prospect Email

  Finds prospect by email address.

• Action
  Stop Follow-Ups

  Stop follow-ups planned for this prospect.

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