Connect Polar to NetHunt CRM

Both apps 56Polar 40NetHunt CRM 16

• Trigger
  Benefit Created

  Triggered when a new benefit is created in Polar.

• Trigger
  Benefit Updated

  Triggered when a benefit is changed in Polar.

• Trigger
  Checkout Created

  Triggered when a new checkout session is created in Polar.

• Trigger
  Checkout Expired

  Triggered when a checkout session expires in Polar without being paid.

• Trigger
  Checkout Updated

  Triggered when a checkout session changes in Polar, for example when it is confirmed or paid.

• Trigger
  Customer Created

  Triggered when a new customer is created in Polar.

• Trigger
  Customer Deleted

  Triggered when a customer is deleted in Polar.

• Trigger
  Customer State Changed

  Triggered when a customer's state changes in Polar - their active subscriptions, granted benefits or meters.

• Trigger
  Customer Updated

  Triggered when a customer's details change in Polar.

• Trigger
  Order Created

  Triggers when a new order is placed in your Polar organization.

• Trigger
  Order Paid

  Triggers when an order in your Polar organization is paid.

• Trigger
  Order Updated

  Triggers when an order in your Polar organization changes.

• Trigger
  Product Created

  Triggers when a new product is created in your Polar organization.

• Trigger
  Product Updated

  Triggers when a product in your Polar organization changes.

• Trigger
  Subscription Active

  Triggers when a subscription in your Polar organization becomes active.

• Trigger
  Subscription Canceled

  Triggers when a customer cancels a subscription in your Polar organization.

• Trigger
  Subscription Created

  Triggers when a new subscription is created in your Polar organization.

• Trigger
  Subscription Past Due

  Triggers when a subscription in your Polar organization falls past due because a payment failed.

• Trigger
  Subscription Revoked

  Triggers when a subscription in your Polar organization is revoked and the customer loses access.

• Trigger
  Subscription Uncanceled

  Triggers when a customer reverses a pending cancellation and keeps a subscription in your Polar organization.

• Trigger
  Subscription Updated

  Triggers when a subscription in your Polar organization changes.

• Action
  Create Benefit

  Creates a benefit in Polar that you can attach to products.

• Action
  Create Checkout Session

  Creates a Polar checkout session for a product and returns the link the customer pays through.

• Action
  Create Customer

  Creates a customer in Polar.

• Action
  Create Discount

  Creates a discount in Polar, either a percentage off or a fixed amount off.

• Action
  Create Product

  Creates a product in Polar with its price or prices.

• Action
  Delete Customer

  Deletes a customer in Polar. Their subscriptions are cancelled and their benefits revoked.

• Action
  Get Checkout Session

  Returns one Polar checkout session by its id, including its status and payment link.

• Action
  Get Customer

  Returns one customer from Polar by their id, including any metadata you stored on them.

• Action
  Get Product

  Returns one product from Polar by its id, with its prices and attached benefits.

• Action
  Get Subscription

  Returns one subscription from Polar by its id, with its status, amount and current period.

• Action
  List Benefits

  Returns a page of benefits from Polar.

• Action
  List Checkout Sessions

  Returns a page of checkout sessions from Polar.

• Action
  List Customers

  Returns a page of customers from Polar.

• Action
  List Discounts

  Returns the discount codes set up in your Polar organization, newest first. You can narrow the list by organization or by name text, and page through the results.

• Action
  List Orders

  Returns the orders placed in your Polar organization. You can narrow the list by product, customer, subscription, checkout, discount or status, and page through the results.

• Action
  List Products

  Returns the products in your Polar organization, with their prices and benefits. You can narrow the list by name text, archived state, one-time versus subscription, or a benefit, and page through the results.

• Action
  List Subscriptions

  Returns the subscriptions in your Polar organization. You can narrow the list by product, customer, discount, active state or status, and page through the results.

• Action
  Update Customer

  Updates an existing Polar customer. Only the fields you fill in are changed; anything left blank keeps its current value.

• Action
  Update Product

  Updates an existing Polar product. Only the fields you fill in are changed; anything left blank keeps its current value.

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