Connect NetHunt CRM to Stripe

Both apps 48NetHunt CRM 16Stripe 32

• 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
  New Charge

  Triggers when a new charge is created.

• Trigger
  New Charge (instant)

  Fires instantly when a charge succeeds in Stripe, via a self-registered webhook (charge.succeeded). The platform registers/deletes the Stripe webhook endpoint automatically at automation activation/deactivation. Payload binds as {{ trigger.body.* }}.

• Trigger
  New Customer

  Triggers when a new customer is created.

• Trigger
  New Event

  Triggers when a new Stripe event is created (covers all event types via the Events API).

• Trigger
  New Invoice

  Triggers when a new invoice is created.

• Trigger
  New paid and available charge

  Triggered when a new paid and available charge is created.

• Trigger
  New paid charge

  Triggered when a new paid charge is created.

• Trigger
  New plan

  Triggered when a new plan is created.

• Trigger
  New Product

  Triggers when a new product is created.

• Trigger
  New Refund

  Triggers when a new refund is created.

• Trigger
  New Subscription

  Triggers when a new subscription is created.

• Action
  Cancel Subscription

  Cancels a subscription by its ID.

• Action
  Create Charge

  Creates a charge. Amount is in the smallest currency unit (e.g. cents).

• Action
  Create charges (bulk charge creation)

  Creates a charge in Stripe.

• Action
  Create Customer

  Creates a new customer in Stripe.

• Action
  Create Payment Intent

  Creates a PaymentIntent (the modern Stripe payment flow). Amount is in the smallest currency unit.

• Action
  Create Price

  Creates a price for a product. unit_amount is in the smallest currency unit.

• Action
  Create Product

  Creates a product (a good or service) in Stripe.

• Action
  Create Refund

  Refunds a charge or payment intent. Provide charge or payment_intent; amount optional for partial refund.

• Action
  Create refund by charge id (distinct from Create Refund)

  Creates a refund for a specific charge id.

• Action
  Create Subscription

  Creates a subscription for a customer to one or more prices.

• Action
  Delete Customer

  Permanently deletes a customer by ID.

• Action
  Find Customer by Email

  Searches for customers matching an email address.

• Action
  Get Charge

  Retrieves a charge by its ID.

• Action
  Get charge details (distinct from Get Charge)

  Retrieves a charge's details by its charge id.

• Action
  Get Customer

  Retrieves a customer by their Stripe ID.

• Action
  Get Invoice

  Retrieves an invoice by its ID.

• Action
  Get Refund

  Retrieves a refund by its ID.

• Action
  Get Subscription

  Retrieves a subscription by its ID.

• Action
  Get transaction details

  Retrieves a transaction's details by its transaction id.

• Action
  List balance transactions

  List balance transactions (txn_xxx) for the account, most recent first.

• Action
  Update Customer

  Updates an existing customer by ID.

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