Most software companies publish a wall of logos and let you assume they all work. This page does the opposite. Every integration below is either built and connectable from your Settings screen today, or it is honestly marked as not built yet. Nothing on this page is a roadmap item dressed up as a feature.
Plan badges show the lowest plan that includes the integration. Core is $199, Grow is $349, Pro is $549, all plus GST per month.
These are the four most requested connectors that do not exist. There is a Request button on each of them inside Pulse, and the request count is what decides the build order. If one of these is a deal-breaker for you, say so before you sign rather than after.
Three ways to get Pulse talking to something we have not connected. Here is exactly what each one can and cannot do.
Seven resources: members, plans, classes, bookings, check-ins, invoices and leads. JSON, cursor pagination, incremental pulls with a since filter, and API keys you create and revoke yourself. Read-only in this version, so you can pull everything out but not write back in. Included on Pro.
Signed POST requests to your endpoint on three events: new member, check-in, and class booking. HMAC signature so you can verify the sender, plus a delivery log in Settings. Payment and cancellation events are not published yet. Included on every plan.
There is no Pulse app in the Zapier directory. You wire it up with "Webhooks by Zapier" plus an API key for pulls, and Pulse outbound webhooks for pushes. It works and people use it, but call it what it is: a wiring job with three triggers, not a one-click install.
Yes, with a limit worth knowing. Pulse pushes paid invoices into Xero and matches contacts by email so you do not get duplicates. It is one-way, Pulse to Xero, not a two-way sync, and it sits on the Pro plan ($549 plus GST per month). If someone tells you it reconciles your bank feed, that is not this integration.
Not a listed Zapier app, no. You can connect Pulse to Zapier using "Webhooks by Zapier" with a Pulse API key to pull data, and Pulse outbound webhooks to trigger Zaps on new member, check-in or class booking. That reaches the wider Zapier ecosystem, but the trigger list is those three events and the setup takes a bit of wiring.
If you run Kisi, yes, and it is one of the better parts of Pulse: memberships activate and revoke door access automatically, including freezes and bans, and door events come back into the member record. If you run Inner Range, Gantner or another RFID controller, there is no Pulse connector today. Ask us before you sign, not after.
Yes, on the Pro plan, and it is read-only in this version. Seven resources (members, plans, classes, bookings, check-ins, invoices, leads), scoped keys you manage yourself, and incremental pulls. You can get all your data out and build reporting on top of it. You cannot create or update records through it yet.
Your member data is yours. Every gym can export members, billing and attendance from inside the app, and Pro adds the Open API for a full programmatic pull. We would rather you never need this page, but you should know the answer before you sign a contract with anyone, including us.
Because you will find out anyway, and it is cheaper for both of us if you find out now. A gym software decision runs for years. If a missing connector is a deal-breaker, we would rather lose the deal in week one than lose your trust in month six.