Integrations and alerts
Connect Whop
Bring Whop sales into Revenue.
Before you start
You need developer-settings access for the correct Whop business.
Step by step
- In Whop, create an API key with custom permissions.
- Include company:basic:read, company:balance:read, payment:basic:read, plan:basic:read, access_pass:basic:read, member:basic:read, and developer:manage_webhook.
- In Nod, open Integrations → Whop → Configure and paste the key.
- Select Connect. Nod validates the connection, registers the webhook, and imports history.
- Review Revenue and associate products with the appropriate delivery.
- Keep prices and checkout in Whop. Subsequent payments, refunds, and cancellations reach Nod through this connection.
Check permissions and delivery
The listed permissions identify the business, read payments and products, and create the automatic notification. A key with only some permissions may fail during connection even if it seems valid. Review the complete list in Whop before pasting it into Nod.
Historical imports may include payments you already know about: check Revenue before recording them again. Prices are configured in Whop; Nod associates payments and products with business delivery. If a product has no program mapping, fix that association before sharing new purchases. Keep the transaction reference to trace an individual payment without exposing keys.
What to expect
You can review imported Whop transactions and their status.
Troubleshooting
An incomplete key can fail even if some data is accessible. Check every listed permission.
Check the buyer’s email if a purchase is not associated with the expected customer. Do not record the same payment twice.