Linking Whop as a source

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

Learn more

Alpha release

This source is currently in alpha. The interface and available tables may change.

The Whop connector syncs memberships, payments, members, and more into the PostHog data warehouse, so you can analyze them alongside your product data.

Prerequisites

Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.

Adding a data source

In PostHog, go to the Sources tab of the data pipeline section.
Click + New source and click Link next to this source.
Enter your credentials (see Configuration below) and click Next.
Select the tables you want to sync, choose a sync method and frequency, then click Import.

Once the syncs are complete, you can start querying this data in PostHog.

Connect your Whop company to sync payments, memberships, members, products, promo codes, invoices, refunds, and disputes. Create a company API key in the Developer tab of your Whop dashboard.

You'll be asked for:

API key: create a company API key in the Developer tab of your Whop dashboard. Grant it read access to the resources you want to sync: company:basic:read, member:basic:read, payment:basic:read, access_pass:basic:read, plan:basic:read, promo_code:basic:read and invoice:basic:read, plus developer:manage_webhook if you want PostHog to register the webhook for you.
Company ID: the ID of the Whop company to sync, shown in your Whop dashboard URL.

Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
Incremental – only new or updated rows are synced on each run, using a cursor field (such as an updated_at timestamp). Cheaper than a full refresh, but deletes aren't captured.
Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See sync methods for a full explanation of how each mode works and how to choose between them.

All Whop tables are full refresh. Each sync replaces the contents of the table.

Configuration

Option	Description
`API key` Type: password Required: True	Create a company API key in the Developer tab of your Whop dashboard. Grant it read access to the resources you want to sync: `company:basic:read`, `member:basic:read`, `payment:basic:read`, `access_pass:basic:read`, `plan:basic:read`, `promo_code:basic:read` and `invoice:basic:read`, plus `developer:manage_webhook` if you want PostHog to register the webhook for you.
`Company ID` Type: text Required: True	The ID of the Whop company to sync, shown in your Whop dashboard URL.

Supported tables

Table	Description	Sync method	Incremental field	Primary key
`memberships`	A membership represents an active relationship between a user and a product. It tracks the user's access, billing status, and renewal schedule.	Webhook, Incremental, Full refresh	created_at	—
`payments`	A payment represents a completed or attempted charge. Payments track the amount, status, currency, and payment method used.	Webhook, Incremental, Full refresh	created_at	—
`members`	A member represents a user's relationship with a company on Whop, including their access level, status, and spending history.	Webhook, Incremental, Full refresh	created_at	—
`products`	A product is a digital good or service sold on Whop. Products contain plans for pricing and experiences for content delivery.	Webhook, Incremental, Full refresh	created_at	—
`entries`	An entry represents a user's signup for a waitlisted plan.	Webhook, Incremental, Full refresh	created_at	—
`invoices`	An invoice represents an itemized bill sent by a company to a customer for a specific product and plan, tracking the amount owed, due date, and payment status.	Webhook, Incremental, Full refresh	created_at	—
`refunds`	A refund represents a full or partial reversal of a payment, including the amount, status, and payment provider.	Webhook, Incremental, Full refresh	created_at	—
`disputes`	A dispute is a chargeback or payment challenge filed against a company, including evidence and response status.	Webhook, Incremental, Full refresh	created_at	—
`dispute_alerts`	A dispute alert represents an early warning notification from a payment processor about a potential dispute or chargeback.	Webhook, Incremental, Full refresh	created_at	—
`setup_intents`	A setup intent allows a user to save a payment method for future use without making an immediate purchase.	Webhook, Incremental, Full refresh	created_at	—
`promo_codes`	A promo code applies a discount to a plan during checkout. Promo codes can be percentage-based or fixed-amount, and can have usage limits and expiration dates.	Incremental, Full refresh	created_at	—
`leads`	A prospective customer who has expressed interest in a company or product but has not yet purchased.	Incremental, Full refresh	created_at	—
`experiences`	An experience is a feature or content module within a product, such as a chat, course, or custom app.	Incremental, Full refresh	created_at	—
`checkout_configurations`	A checkout configuration is a reusable configuration for a checkout, including the plan, affiliate, and custom metadata. Payments and memberships created from a checkout session inherit its metadata.	Full refresh	—	—
`affiliates`	An affiliate tracks a user's referral performance and commission earnings for a company, including retention rates, revenue metrics, and payout configurations.	Full refresh	—	—
`shipments`	A physical shipment associated with a payment, including carrier details and tracking information.	Webhook, Full refresh	—	—
`company_token_transactions`	A token transaction records a credit or debit to a member's token balance within a company, including transfers between members.	Full refresh	—	—

Troubleshooting

If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.

If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.