Skip to main content

Integrate TeamBuildr OS with Kisi

TeamBuildr OS is a member management platform for fitness facilities, performance centers, personal training facilities, and other fitness businesses. When combined with Kisi, you can automatically grant or revoke member access based on their membership type and status using Zapier to customize your permissions and access.

info

This integration is based on Kisi's Zapier integration.

Prerequisites​

  • Kisi organization administrator rights
  • TeamBuildr OS account with Owner access and permission to manage integrations
  • Memberships and/or packages created in your TeamBuildr OS account
  • A Zapier subscription (Pro plan recommended)

Generate a Kisi API key​

You need to have organization administrator or organization owner rights to create an API key. We recommend creating API keys from the organization owner's account, to avoid the API key becoming invalid when an organization admin loses their admin rights.

  1. Sign in to Kisi
  2. On the top right corner, click on your name and click on My Account
  3. Next, select the API tab and click on Add API Key
  4. Enter the name for the API key and your Kisi password and click Add
  5. Copy the API key shown on the screen and click Close

Set up the integration​

There is no direct integration setup workflow within TeamBuildr OS itself. All integration is handled via Zapier.

  1. Sign in to Zapier
  2. Click Create and select Zap
  3. Select TeamBuildr OS as the trigger app and authenticate using your TeamBuildr OS login credentials
  4. Select Kisi as the action app and authenticate using your Kisi API key
info

This authentication only needs to be done once. All future Zaps involving TeamBuildr OS or Kisi will recall your prior authentication.

Follow the instructions to set up a Kisi action in Zapier.

Set up the following Zaps to cover the full member lifecycle:

Grant access when a member is created​

Creates a user in Kisi and sends them an access invite for the appropriate group using the Create Invite action.

Grant access when a transaction is completed​

TeamBuildr OS passes the specific membership or package purchased, allowing you to map each to the appropriate Kisi group using the Create Invite action.

Revoke access when a membership is cancelled or a package expires​

Kisi's Delete User action requires a User ID rather than an email address. The Fetch Users step looks up the user by email and returns the User ID needed for the final step.

note

If different membership types require different access levels, create a separate Zap for each membership or package type. Each package with a defined end date also requires its own Zap to revoke access on expiry.

TeamBuildr OS also provides additional Zapier triggers that can be used to build further automations:

  • First Successful Member Transaction — triggers when a member completes their first member-initiated checkout
  • Member Booking Sign In — triggers when a member is signed into a class, workshop, or appointment they have booked
  • New Staff Profile Created — triggers when a new owner, admin, teacher, or front desk staff profile is created

Limitations​

  • Access cannot be restricted based on payment status — temporary suspension due to failed payments is not supported
  • Access cannot be restricted based on remaining credits — if a membership runs out of credits before expiring, access is not automatically revoked
Last updated on by Timofejs Golubevs