Integrations
What BookClay plugs into, and what each one does
Short list on purpose. Everything below either runs in production today or is labelled as not built yet, because a logo wall that quietly includes roadmap items is how software loses trust in week two.
Payments
Stripe Connect
LiveTakes the money, into your account
You connect your own Stripe account in about three minutes. Class fees, memberships, gift cards and point-of-sale charges settle directly to your bank. BookClay is never the merchant of record and never holds your funds. If you already use Stripe, it is the same account.
Stripe Billing
LiveRecurring membership dues
Membership plans become Stripe subscriptions on your account. Renewals, prorations, failed-card retries and cancellations all reflect back into BookClay through signed webhooks, so the member list and Stripe never drift apart.
Stripe Terminal
LiveCard present, at the counter
Point of sale for clay, tools, glaze and firing fees runs on Stripe Terminal, so counter sales land in the same ledger as everything booked online.
Messaging
Twilio
LiveTexts, on your own studio number
Bring your own Twilio number and BookClay handles inbound and outbound SMS: the AI front desk, pickup notices, class reminders, retention messages and broadcasts. Inbound webhooks are signature-verified. STOP handling and opt-out records are automatic.
Resend
LiveTransactional email
Booking confirmations, receipts, magic-link sign-ins and the weekly digest. Email is the default channel, so a studio that never wants to deal with SMS registration can run the whole product without Twilio at all.
SendGrid
LiveEmail fallback
Configured as a second sender. If the primary provider has an incident, transactional mail keeps going out rather than queuing silently.
Marketing
Klaviyo
LiveTwo-way audience sync
Paste an API key, pick a list, and members and leads flow into Klaviyo with their consent state intact. Opt-outs that happen in Klaviyo come back and suppress in BookClay, so an unsubscribe means the same thing in both systems.
Mailchimp
LiveTwo-way audience sync
The same connection as Klaviyo, against a Mailchimp audience. Key is verified before anything is written and stored encrypted at rest.
Commerce
Shopify
LiveCustom-app token, or the BookClay app
Two ways to connect a store. Paste a custom-app Admin API token, or install the BookClay app (OAuth with HMAC and a one-time state, scopes limited to read_orders, read_products, and read_customers). The shop token is encrypted. Once you confirm which products are classes, paid orders become bookings. App uninstall and the three mandatory GDPR webhooks are handled. Public app review has not been submitted.
Wix
LiveConnect a Wix site
Install the BookClay app on a Wix site from Settings. Contacts and site members become members, and paid Wix orders become payment records. The access token is encrypted. Removing the app in Wix deletes the connection and erases imported contact details. The booking embed still works on a Wix page without this connection.
Square
LiveSandbox card payments
An owner can connect their own Square sandbox account and choose Square instead of Stripe for class bookings, priced drop-ins, and the first period of a membership. Class packs stay on Stripe. Tokens are encrypted per studio. Production charges are refused until reviewed. Studios that never connect Square stay on Stripe.
Platform
Clerk
LiveStaff accounts and roles
Owner, assistant and instructor roles with organization-scoped sessions. The studio a request is allowed to touch is resolved from the signed-in organization, never from a URL parameter, which is what keeps one studio out of another studio’s data.
Build your own
Outbound webhooks
LivePush events anywhere
Seven events today: member created, booking confirmed, booking canceled, subscription created, subscription canceled, lead created, lead converted. Each delivery is signed HMAC-SHA256 so you can verify it came from us, with a delivery log and automatic pause after repeated failures.
REST API
LiveRead and write your own data
API-key authenticated endpoints for classes, bookings, members, the kiln queue and messages. Enough to wire BookClay into a Zapier or n8n flow, a custom site, or whatever you already run.
Embed widget
LiveBooking on the site you already have
A snippet you paste into Squarespace, WordPress, Wix or anything else. It renders your booking or membership signup inline and resizes itself. You do not have to move your website to use BookClay.
Planned
Asked for often enough to name. Not shipped.
Google Calendar
Not built yetPush the class schedule to a calendar
Not built yet. The schedule is available over the API in the meantime, which is how a couple of people are already doing this.
QuickBooks
Not built yetSync revenue to the books
Not built yet. Exports are CSV today and Stripe already reconciles cleanly, which covers most of what studios ask for here.
Missing something
If the thing you need is not here, say so
There is no integrations team to route the request to. It goes to the person who writes the code, and small ones tend to get built in days rather than quarters.
In the meantime
- The REST API covers classes, bookings, members, kiln and messages, which is enough to build most of what people ask for on top.
- Signed outbound webhooks push events into Zapier, n8n or your own endpoint the moment they happen.
- Everything exports as CSV, self-serve, any time.