Connect SureCart to NetHunt CRM

Both apps 86SureCart 70NetHunt CRM 16

• Trigger
  Affiliation Request Approved

  Triggers when a affiliation request is approved.

• Trigger
  Affiliation Request Created

  Triggers when a affiliation request is created.

• Trigger
  Affiliation Request Denied

  Triggers when a new affiliation request is denied.

• Trigger
  Cancellation Act Created

  Triggers when a cancellation act is created.

• Trigger
  Cancellation Act Updated

  Triggers when a cancellation act is updated.

• Trigger
  Customer Created

  Triggers when a customer is created.

• Trigger
  Customer Updated

  Triggers when a customer is updated.

• Trigger
  Fulfillment Created

  Triggers when a fulfillment is created.

• Trigger
  Fulfillment Deleted

  Triggers when a fulfillment is deleted.

• Trigger
  Fulfillment Updated

  Triggers when a fulfillment is updated.

• Trigger
  Order Created

  Triggers when a order is created.

• Trigger
  Order Delivered

  Triggers when a order is delivered.

• Trigger
  Order Fulfilled

  Triggers when a order is fulfilled.

• Trigger
  Order Paid

  Triggers when a order is paid.

• Trigger
  Order Partially Fulfilled

  Triggers when a order is partially fulfilled.

• Trigger
  Order Partially Shipped

  Triggers when a order is partially shipped.

• Trigger
  Order Payment Failed

  Triggers when a order payment fails.

• Trigger
  Order Processing

  Triggers when a order becomes processing.

• Trigger
  Order Shipped

  Triggers when a order is shipped.

• Trigger
  Order Unfulfilled

  Triggers when a order is unfulfilled.

• Trigger
  Order Voided

  Triggers when a order is voided.

• Trigger
  Payout Completed

  Triggers when a payout is completed.

• Trigger
  Purchase Created

  Triggers when a purchase is created.

• Trigger
  Purchase Invoked

  Triggers when a purchase is invoked.

• Trigger
  Purchase Revoked

  Triggers when a purchase is revoked.

• Trigger
  Purchase Updated

  Triggers when a purchase is updated.

• Trigger
  Referral Approved

  Triggers when a referral is approved.

• Trigger
  Referral Created

  Triggers when a referral is created.

• Trigger
  Refund Created

  Triggers when a refund is created.

• Trigger
  Refund Succeeded

  Triggers when a refund succeeds.

• Trigger
  Return Request Completed

  Triggers when a return request is completed.

• Trigger
  Return Request Created

  Triggers when a return request is created.

• Trigger
  Return Request Deleted

  Triggers when a return request is deleted.

• Trigger
  Return Request Opened

  Triggers when a return request is opened.

• Trigger
  Return Request Updated

  Triggers when a return request is updated.

• Trigger
  Subscription Active

  Triggers when a subscription becomes active.

• Trigger
  Subscription Canceled

  Triggers when a subscription is canceled.

• Trigger
  Subscription Completed

  Triggers when a subscription is completed.

• Trigger
  Subscription Created

  Triggers when a subscription is created.

• Trigger
  Subscription Past Due

  Triggers when a subscription becomes past due.

• Trigger
  Subscription Renewed

  Triggers when a subscription is renewed.

• Trigger
  Subscription Set to Cancel

  Triggers when a subscription is set to cancel.

• Trigger
  Subscription Trialing

  Triggers when a subscription becomes trialing.

• Trigger
  Subscription Updated

  Triggers when a subscription is updated.

• Action
  Find Affiliation

  Find an existing affiliation by ID.

• Action
  Find Affiliation Request

  Find an existing affiliation request by ID.

• Action
  Find Cancellation Act

  Find an existing cancellation act by ID.

• Action
  Find Checkout

  Find an existing checkout by ID.

• Action
  Find Click

  Find an existing click by ID.

• Action
  Find Coupon

  Find an existing coupon by ID.

• Action
  Find Customer

  Find an existing customer by ID.

• Action
  Find Fulfillment

  Find an existing fulfillment by ID.

• Action
  Find Fulfillment Item

  Find an existing fulfillment item by ID.

• Action
  Find Line Item

  Find an existing line item by ID.

• Action
  Find Order

  Find an existing order by ID.

• Action
  Find Payment Intent

  Find an existing payment intent by ID.

• Action
  Find Payment Method

  Find an existing payment method by ID.

• Action
  Find Payout

  Find an existing payout by ID.

• Action
  Find Payout Group

  Find an existing payout group by ID.

• Action
  Find Price

  Find an existing price by ID.

• Action
  Find Product

  Find an existing product by ID.

• Action
  Find Promotion

  Find an existing promotion by ID.

• Action
  Find Purchase

  Find an existing purchase by ID.

• Action
  Find Referral

  Find an existing referral by ID.

• Action
  Find Referral Item

  Find an existing referral item by ID.

• Action
  Find Refund

  Find an existing refund by ID.

• Action
  Find Return Item

  Find an existing return item by ID.

• Action
  Find Return Request

  Find an existing return request by ID.

• Action
  Find Subscription

  Find an existing subscription by ID.

• Action
  Find Tracking

  Find an existing tracking by ID.

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