Connect NetHunt CRM to Resend

Both apps 44NetHunt CRM 16Resend 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.

• Action
  Add Contact to Segment

  Adds a contact to a Resend segment. You can identify the contact by its ID or email address.

• Action
  Add Suppression

  Adds an email address to your Resend suppression list so no further mail is sent to it.

• Action
  Cancel Email

  Cancels a scheduled Resend email that has not been sent yet.

• Action
  Create API Key

  Creates a new Resend API key. The key itself is returned once, so store it right away.

• Action
  Create Contact

  Creates a contact in Resend. Returns the new contact's ID.

• Action
  Create Domain

  Adds a sending domain to Resend. Returns the DNS records you need to add at your domain host to verify it.

• Action
  Create Segment

  Creates a new segment in Resend for grouping contacts.

• Action
  Delete API Key

  Deletes a Resend API key so it can no longer be used.

• Action
  Delete Contact

  Deletes a contact from Resend. You can identify the contact by its ID or email address.

• Action
  Delete Domain

  Removes a sending domain from Resend.

• Action
  Delete Segment

  Deletes a segment from Resend. The contacts themselves are not deleted.

• Action
  List API Keys

  Returns the API keys on your Resend account, with each key's name and when it was last used. The key values themselves are never returned.

• Action
  List Contacts

  Returns the contacts in your Resend account, optionally limited to one segment.

• Action
  List Domains

  Returns the sending domains on your Resend account and each one's verification status.

• Action
  List Segments

  Returns the contact segments in your Resend account.

• Action
  List Sent Emails

  Returns the emails you have sent through Resend, newest first, with each email's id, sender, recipients, subject, send time and latest delivery event. Supports paging before or after a given email id.

• Action
  List Suppressions

  Returns the email addresses on your Resend suppression list, showing for each one the address, why it was suppressed (bounce, complaint or added manually), the email that triggered it and when it was added.

• Action
  Remove Contact From Segment

  Removes a contact from one of your Resend segments. Identify the contact by its ID or by its email address, and name the segment to take it out of. The contact itself is not deleted.

• Action
  Remove Suppression

  Takes an email address off your Resend suppression list so you can send to it again. Identify it by the suppression ID or by the email address itself.

• Action
  Retrieve Contact

  Returns one contact from your Resend audience, including their name, email address, whether they have unsubscribed, when they were added, and any custom properties stored on them. Look the contact up by its ID or by its email address.

• Action
  Retrieve Domain

  Returns one of your Resend sending domains, including its name, verification status, sending region, tracking settings and the DNS records it needs with each record's current status.

• Action
  Retrieve Segment

  Returns one of your Resend segments by its ID, with the segment's name and when it was created.

• Action
  Retrieve Sent Email

  Returns one email you sent through Resend, with its sender, recipients, subject, HTML and text body, tags, send time and latest delivery event.

• Action
  Send Batch Emails

  Sends up to 100 emails through Resend in a single call. Give it a list of emails, each with a sender, recipients, subject and body, and it returns the id of every email it created.

• Action
  Send Email

  Sends an email through Resend. Set the sender, recipients and subject, provide an HTML or plain text body, and optionally add CC/BCC, reply-to, attachments, tags or a send time.

• Action
  Update Contact

  Updates a contact in your Resend audience. Identify the contact by ID or email address, then change the name, the subscribed/unsubscribed state, or the custom properties. Anything you leave blank stays as it is.

• Action
  Update Email

  Reschedules an email you already queued in Resend, moving it to a new send date and time. Only emails that have not gone out yet can be changed.

• Action
  Verify Domain

  Asks Resend to re-check the DNS records for one of your sending domains and start verifying it. Verification runs in the background, so the domain shows as pending until it finishes.

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