Connect Whop to NetHunt CRM

Both apps 61Whop 45NetHunt CRM 16

• Trigger
  Dispute Updated

  Triggers when a payment dispute on your Whop account changes, for example when its status moves or the deadline to respond is set.

• Trigger
  Failed Payment

  Triggers when a payment on your Whop account fails, giving you the amount, the reason it failed and when Whop will try again.

• Trigger
  Invoice Paid

  Triggers when an invoice on your Whop account is paid, giving you the invoice, its amount and who paid it.

• Trigger
  Invoice Past Due

  Triggers when an invoice on your Whop account passes its due date without being paid.

• Trigger
  Membership Canceled

  Triggers when a Whop membership ends and the customer loses access, whether they cancelled or their payments stopped.

• Trigger
  Membership Scheduled to Cancel

  Triggers when a Whop customer schedules their membership to end at the close of the current billing period, or reverses that decision.

• Trigger
  New Dispute

  Triggers when a buyer opens a new chargeback dispute on a Whop payment.

• Trigger
  New Dispute Alert

  Triggers when Whop receives an early dispute alert from the card network, before a formal chargeback is opened.

• Trigger
  New Invoice

  Triggers when a new invoice is created for a customer in Whop.

• Trigger
  New Member Joined

  Triggers when a new member joins — a Whop membership becomes active for a customer.

• Trigger
  New Payment

  Triggers when a new payment is created in Whop.

• Trigger
  New Waitlist

  Triggers when someone signs up for a waitlisted plan in Whop, creating a new waitlist entry.

• Trigger
  Payment Method Saved

  Triggers when a customer successfully saves a payment method in Whop for future use.

• Trigger
  Payment Pending

  Triggers when a Whop payment moves into a pending state, waiting to clear.

• Trigger
  Payment Refunded

  Triggers when a payment is refunded in Whop.

• Trigger
  Waitlist Approved

  Triggers when a waitlist entry is approved in Whop, granting the person access to the plan.

• Action
  Add Free Days to Membership

  Adds free days to a Whop membership, pushing out its next renewal date, expiration or trial. Useful for service credits, support gestures and referral rewards.

• Action
  Approve Waitlist

  Approves a pending waitlist entry in Whop so the applicant is granted access. Whop processes the approval in the background and returns a job ID.

• Action
  Cancel Membership

  Cancels a Whop membership, either at the end of the current billing period or straight away.

• Action
  Create Checkout Session

  Creates a Whop checkout session for a plan and returns the purchase link you send the customer to.

• Action
  Create Invoice

  Creates an invoice in Whop for a new or existing customer, either emailed as a payment link or charged automatically. Anything you leave blank is left out of the request.

• Action
  Create Lead

  Creates a lead in Whop to track someone who showed interest in a product, along with where they came from.

• Action
  Create Payment

  Charges a Whop member's saved payment method, either for an existing plan or for a new plan you describe inline. Anything you leave blank is left out of the request.

• Action
  Create Promo Code

  Creates a discount code customers can enter at checkout on Whop, as either a percentage or a flat amount off, with optional limits on who can use it and how often.

• Action
  Deny Waitlist

  Denies a pending waitlist entry in Whop so the applicant is turned down, and returns the updated entry.

• Action
  Find Entries

  Finds waitlist entries on your Whop account, with optional filters for status, product, plan and when they were submitted.

• Action
  Find Entry

  Looks up a single Whop waitlist entry by its ID and returns its status, who applied and what they applied for.

• Action
  Find Invoice

  Looks up a single Whop invoice by its ID and returns its status, amount, line items and who it was sent to.

• Action
  Find Lead

  Looks up a single Whop lead by its ID and returns who they are, what they were interested in and whether they have become a paying customer.

• Action
  Find Member

  Looks up a single member of your Whop company by ID and returns their contact details, access level and how much they have spent.

• Action
  Find Membership

  Looks up a single Whop membership by its ID and returns its status, renewal dates, the customer and what they are subscribed to.

• Action
  Find Payment

  Looks up a single Whop payment by its ID and returns its status, amounts, card details and what it was for.

• Action
  Find Plan

  Looks up a single Whop plan by its ID and returns its pricing, billing period, visibility and purchase link.

• Action
  Find Product

  Looks up a single Whop product by its ID and returns its name, visibility, member count and store details.

• Action
  Find Products

  Lists the products on your Whop company, with optional filters for visibility and paging.

• Action
  Find Refund

  Looks up a single Whop refund by its ID and returns the amount, its processing status and the payment it came from.

• Action
  Get Payment Fees

  Lists the fees taken out of a Whop payment, such as processing and affiliate fees, with the amount and type of each.

• Action
  Pause Membership

  Pauses billing on a Whop membership, optionally resuming automatically on a date you choose.

• Action
  Refund Payment

  Refunds a Whop payment in full, or by a partial amount you specify.

• Action
  Resume Membership

  Resumes billing on a Whop membership that was paused.

• Action
  Unarchive Affiliate

  Restores an archived Whop affiliate so they can earn commissions again.

• Action
  Uncancel Membership

  Reverses a pending cancellation so a Whop membership keeps renewing.

• Action
  Update Lead

  Updates the referrer or your own stored data on an existing Whop lead.

• Action
  Update Membership

  Updates your own stored data on an existing Whop membership.

• Action
  Void Invoice

  Voids a Whop invoice so it can no longer be paid.

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