Ship integrations faster
Build customer automations without heavy engineering effort.
Club OS Connector
Build embedded workflows that sync Club OS leads, members, appointments and KPIs with your app. Deliver in-app automations—lead capture, appointment booking and member sync—without adding to your core product backlog.
Reusable orchestration
Create one workflow and run it across many customer accounts.
Governed MCP tools
Expose approved Club OS actions as controlled tools for users.
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Overview
Teams can integrate Club OS to sync leads, prospects, members, appointments, follow-ups and KPIs between Club OS and your product. The Club OS API exposes endpoints for authentication, leads, appointments, members and KPIs—letting you read, create and update those records from orchestrated Cyclr workflows. (s3.amazonaws.com)
PRODUCT USE CASES
Top use cases
Cyclr helps citizen integrators and engineering teams convert API endpoints into reusable, multi-tenant integrations—turning Club OS leads, appointments and member objects into business workflows your customers can configure and use.
Auto-create Club OS prospects from your app
Create or find leads in Club OS when users submit forms, then schedule an appointment on their calendar (leads, appointments). (zapier.com)
Book and manage appointments
Create, edit and cancel Club OS appointments from your app or scheduling UI, keeping calendars in sync. (zapier.com)
Sync member and membership records
Provision or update member profiles and membership agreements across systems to keep billing and access current. (s3.amazonaws.com)
ORCHESTRATION
How Club OS works with Cyclr
Cyclr sits between your SaaS product and Club OS to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
Club OS
Club OS processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore Club OS methods you can orchestrate through Cyclr.
Lookup3
Get Email Match
ActionGets the Member ID for the specified email.
List Locations
ActionLists locations that your account can access.
List Services
ActionLists services that your account can access.
Prospects4
Update Prospect
ActionUpdate an existing prospect. The prospect will be looked up by name, email and phone number(s).
Get Prospect
ActionVerifies that the given prospect userId exists in Club OS and you have access to it.
Create Referral
ActionAdd a referrals to the system. Referrals will only be added if they are not already in the system. We match based on email or phone number. The memberEmail must be attached to a member within a club in which you are authorized.
Create Prospect
ActionAdd a prospect to the system. Prospect home phone number. Email or 1 phone number is required.
TECHNICAL DETAILS
Club OS integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing Club OS integrations in Cyclr.
API and authentication
- API host
https://api2.club-os.com- Authentication
- Token (username/password)
- Credentials
Username and password to request a 24-hour token; Club and Location IDs may also be required.
- Method categories
Leads, members, prospects, appointments, follow-ups, memberships, KPIs
Pagination and rate limits
Pagination
API returns up to 1,000 results per request; use the offset parameter to page further. (clubos.helpjuice.com)
Rate limits
Refer to the vendor API documentation for current limits.
IMPLEMENTATION
Authentication at a glance
Club OS issues a token via GET /authenticate?username={username}&password={password}; include Authorization header on requests. Token typically lasts 24 hours. Confirm which auth option Cyclr enables in Console. (clubos.helpjuice.com)
- Authentication method
- Token (username/password)
- Credential required
Username and password to request a 24-hour token; Club and Location IDs may also be required.
Before you begin:
View setup guideRequires a Club OS account and API access; request API credentials from Club OS support. (clubos.helpjuice.com)
COMMON QUESTIONS
Frequently asked questions
It syncs Club OS leads, prospects, members, appointments, follow-ups and KPIs. Use Cyclr workflows to create, update or query those records and trigger downstream actions in your product. (s3.amazonaws.com)
You obtain a short-lived token by calling /authenticate with a username and password and include that token in the Authorization header on requests; tokens are typically valid 24 hours. Confirm Cyclr’s auth storage option in Console. (clubos.helpjuice.com)
Yes. Cyclr runs multi-tenant workflows so you can reuse orchestration across customer accounts while keeping credentials and data separated per tenant. Ensure each customer has the required Club OS API credentials. (club-os.com)
Yes. Cyclr can expose approved Club OS actions as governed MCP tools for product teams to control which operations end users can run. Map Club OS endpoints to MCP tools during orchestration design. (s3.amazonaws.com)
KEEP EXPLORING
Related resources and connectors
Documentation
What is iPaaS?
Read more →ProductTeaming up your POS and eCommerce Integrations
Read more →ProductMCP PaaS
Read more →Related connectorAlertMedia
Related Marketing connector for customer-facing integration workflows.
Related connectorOpSuite
Related Marketing connector for customer-facing integration workflows.
Related connectorAmazon Selling Partner
Related Marketing connector for customer-facing integration workflows.