GoTeamUp

Create the access shell first

In GoTeamUp, create the membership your RevKeen customers will be granted: a prepaid plan (or pack) with the price, joining fee, and penalties all set to zero, proration off, and no GoTeamUp payment plan. Give it the same number of classes, validity period and eligible classes as the product you sell, and start it on the date of purchase. Turn on sharing if it is a shared class pass. Prefer hiding it or making it provider-only so members cannot buy it in GoTeamUp. RevKeen prices and collects; the GoTeamUp membership is only the access record. Priced GoTeamUp plans cannot be used as grant targets.

Connect your business

Use the TeamUp app in the RevKeen marketplace and the per-business M2M token issued for your GoTeamUp business. Connection Manager stores the credential securely for that merchant. Do not share one token across merchants or use a Teamup Calendar connection. This is direct M2M authentication, not Better Auth or the Nango Calendar integration.

Confirm the intended business before saving. Keep the token out of tickets and screenshots. When rotating it, update the same merchant connection and verify status before resuming sync.

Map and reconcile

Sync imports your zero-money GoTeamUp memberships as unpriced RevKeen products. Set each product's price in RevKeen, then bind it to its GoTeamUp membership in the app's Access products section. The integration covers customers, zero-money memberships, classes, and bookings; RevKeen owns billing. Priced TeamUp plans are surfaced for operator review to avoid billing in both systems.

How customers buy and book

Sell through RevKeen, not the TeamUp store. Put a RevKeen Checkout link for each product on your own website, for example on a Packages section's buttons. Keep the GoTeamUp schedule embed for booking. The GoTeamUp widget stays your timetable, login and app; its Buy button cannot hand a customer over to RevKeen, so do not sell mapped products through it.

After a confirmed RevKeen payment, RevKeen:

• finds the customer in GoTeamUp by the email they paid with, or creates them if they are new. GoTeamUp emails a new customer an invitation to set up their login;
• grants the mapped zero-money membership. Every pack bought is its own GoTeamUp membership, so a second pack or two packs in one basket each give the customer their own classes;
• shows the customer, on the confirmation page and the receipt, that they can log in to GoTeamUp with the same email to book.

A replayed payment never creates a second membership. RevKeen never charges through GoTeamUp.

If RevKeen cannot grant access, for example because two GoTeamUp customers share the email, it does not guess. You get an inbox alert with the payment, and the customer is told their access is being set up. Grant it by hand in GoTeamUp, and fix the cause (for example the duplicate customer) before the next sale.

Cancellations and refunds

Cancel in RevKeen, from the customer portal or your dashboard. RevKeen then cancels the GoTeamUp membership: immediately for an immediate cancellation, or when a period-end cancellation takes effect. It does the same when a subscription ends after failed payments.

A full refund of a pack cancels that pack in GoTeamUp. A partial refund leaves access in place and sends you an alert to decide. Cancelling a shared pack also removes access for anyone it was shared with.

Cancelling only in GoTeamUp does not stop RevKeen billing. Always cancel in RevKeen.

Start with a small known set. Compare customer identity, membership/package mapping, class/booking status, and the RevKeen billing result. Resolve unmapped or priced plans before treating sync as complete. Re-running sync must reconcile existing identities rather than create a duplicate customer or subscription.

Support and reconnect

Check connection status, the affected source record, mapping, and last sync outcome. For an expired/revoked M2M token, reconnect the same business and inspect a bounded sample. Give support redacted record IDs and timestamps, never the token. Credential refresh and internal repair endpoints are not public integration APIs.

Related: PracticeHub and Wodify.

Owner: david · Reviewed 30 Sep 2026 · Next review 29 Dec 2026