#Integrate Whop

Create an inbound integration in Clickmax, paste your Whop API Token, and register the generated URL in a Whop webhook. From then on every event carrying an email creates or updates a contact (tagged whop), and approved payments become sales in Clickmax.

Before you start

• Workspace role: Owner, Admin, Editor or Collaborator. Finance, Guest and Attendant have no access to Integrations.
• Plan:
• From your Whop account you need an API key created with the Admin role. Clickmax reads your account and your Whop product catalog; with a lower role those reads fail and the product picker comes back empty.
• The key also needs to read the member's email — without it Clickmax cannot identify the buyer and drops the event.
• The webhook Token (the signing secret) is generated by Whop itself when you create the webhook, so it only exists after step 6.

#Step by step

1. In Clickmax, open Integrations and select the Whop card.
2. In another tab, go to the Whop dashboard and sign in to your seller account.
3. In Whop, go to Developer > Account API Keys > Create. Under Inherit role permissions, pick Admin and copy the key (whop_…).
4. In Clickmax, paste the key into the API Token field, name the integration and, in the Token field, paste any temporary value — it will be replaced by the signing secret in step 8. Click Create integration.
5. Clickmax generates a webhook URL. Copy it.
6. In Whop, go to Developer > Webhooks > Create webhook and paste the copied URL.
7. Select the events you want to receive. Check them all for a complete history — the table in What starts arriving shows what each one does in Clickmax.
8. Copy the signing secret shown in the Secret column of the webhooks table, return to Clickmax and replace the Token field value with the copied secret.
9. Click Finish integration.

#What starts arriving

Every event carrying an email creates or updates a contact tagged whop, records an activity in the contact history and can fire automations. Some of them also record a sale.

Points that usually raise questions:

• An approved payment and a paid invoice mark the contact as a customer. So does a subscription activation.
• A pending payment (payment.pending) is the window while Whop is still settling the charge, such as a bank transfer. The sale enters with the Pending status and moves to Paid or Failed once Whop confirms — always the same sale, never two.
• A pending sale does not count as revenue. Revenue indicators, average ticket and contact LTV only add up paid sales.
• A refund only changes the sale once it settles. A refund that was opened or that failed fires the automation and shows in the history, but leaves the sale status untouched.
• Subscriptions and invoices never record a sale. Each cycle is charged by its own payment, and an invoice is settled by a payment — recording both would count the same money twice.
• A subscription renewal arrives as a new approved payment, so each billed cycle is its own sale.
• Scheduled cancellation and undone cancellation are separate triggers. Whop uses a single event (membership.cancel_at_period_end_changed) for both directions and Clickmax splits it — so a retention automation never fires for someone who has just decided to stay.
• Events without the buyer's email are ignored, because the contact cannot be identified without it.

#Currency

The sale keeps the currency Whop charged in, and the sales screens show the value in it. When you sell in more than one currency the indicators show one currency at a time — adding different currencies into a single total would mean nothing — and a selector lets you switch between them.

Charges in crypto (BTC, ETH, APE) and gold (XAU) are recorded, but very small values may show as zero: Clickmax stores values with two decimal places.

#Filtering by product

On the triggers you can filter by product: Clickmax lists products straight from your Whop account using the API Token.

If you have more than one Whop integration in the same workspace, each one uses its own API Token and therefore shows that account's catalog. An Account field then appears above the product so you can pick which integration to list from. With a single integration the field is hidden.

#Related

• All integrations
• Create your first automation — react to Whop payments
• Integrate Guru and Integrate Yever

#If it didn't work

• I can't create the integration: check that the value pasted into the API Token field is a valid Whop API key, created under Developer > Account API Keys. See the error codes.
• No events arrive: check that the Token field holds the signing secret Whop showed when you created the webhook — a mismatched secret makes Clickmax reject the delivery. See the error codes.
• A specific event doesn't arrive: events without the buyer's email are discarded (Clickmax cannot resolve the contact). Check that the API key has the member-email read permission. See the error codes.
• Nothing arrives even with the right secret: check the API version you picked when creating the webhook in Whop. The integration expects the payload format where the product and the buyer are nested inside the event; if you selected a newer version, recreate the webhook keeping the default version.
• The sale is stuck on Pending: Whop only sends the confirmation once settlement finishes. Check in Whop whether the payment left "pending"; if it did and Clickmax did not update, make sure the payment.succeeded and payment.failed events are selected on the webhook.