Send your bookings to the other apps you use.
Zapier connects FullClass to a few thousand other tools, and nobody has to write code. A booking can become a row in your spreadsheet, or a payment can show up in your accounting tool, seconds after it happens.
Best for: businesses already keeping something up to date by hand outside FullClass, and anyone whose next question starts with "can it also send this to...".
For the tools we don't connect to directly.
Every business runs something its booking software doesn't, like the team channel the front desk watches all day. Keeping it current usually means somebody retyping the same booking, or waiting for a feature request to reach the top of somebody else's list.
With Zapier you don't have to wait for us. You decide where each booking, payment or cancellation goes, and nobody has to retype it.
Your Zaps in FullClass
SettingsThe moments that can start a Zap.
The same event can feed as many Zaps as you like. FullClass sends each one the moment it happens, so a booking reaches your Zap in seconds, not on a fifteen-minute cycle.
- A booking is confirmed. Only once the booking is confirmed, so a checkout somebody abandoned halfway never reaches your spreadsheet.
- A booking is changed. Moved to another class, or edited by your team: its payment status, payment method or notes. The Zap is told what changed, and which class a moved booking left.
- A booking is canceled. However it happened: the customer canceled from their portal, your team canceled in the admin, or a refund came back from your payment provider.
- A customer checks in. When your team checks someone in to their class, by hand or by scanning their QR code. A good moment for a thank-you or a review request.
- A customer account is created. Whichever route they came in by: booking online, buying a gift card, signing up themselves, added by your team, or brought over in an import.
- Money came in. A class booking, a private event, or a gift card, including the offline payments your team records by hand.
- A refund is issued. Money going back to a customer for a booking, a gift card or a private event, including refunds made in Stripe or Square and lost chargebacks.
- A class is scheduled. Every class you add, whether it's a one-off, part of a weekly series or part of a course. Use it to announce new dates.
- A class is changed. Rescheduled, moved to another location, given another instructor, repriced or resized. A reschedule carries the old times too, so a calendar Zap can find the entry to move.
- A class is canceled. The whole class, with how many bookings it ended and how much was refunded. Each of those bookings also sends its own cancellation.
- A waitlist spot was offered. Someone canceled, and FullClass offered their seat to the next person waiting.
- A course is bought. Once for the whole course, with its full price and every session, so a sales Zap records one sale rather than one per session.
- A course purchase changes. A session canceled, a refund, a course booked to pay later now paid, or a card dispute. The Zap is told what changed.
- A course purchase is canceled. The whole course at once, or its last session, with who canceled it and how much was refunded.
Everything else plugs in behind it.
A booking, a cancellation, a new customer, a payment or a waitlist offer leaves FullClass once and your Zaps take it wherever you need it, such as Google Sheets, Slack, Gmail, QuickBooks, Google Drive, HubSpot and a few thousand more.
From a key to a running Zap.
Create a restricted key
Under Settings, then API keys, create a secret key, choose Restricted and tick the Zapier preset, then untick anything your Zaps will not use. It's the only credential the connection needs. It can't cancel or refund a booking, and you can revoke it from the same page.
Connect FullClass in Zapier
Paste the key once. Zapier labels the connection with your business name, so an account you manage alongside others stays easy to tell apart.
Pick a trigger and what follows it
Choose an event, then choose what should happen next from Zapier's catalog. Filters and extra steps are up to Zapier, and FullClass doesn't limit them.
Turn it on and watch it
Switching the Zap on registers it under Settings, then Webhooks, badged as managed by Zapier, with the same delivery log and retry history as any other endpoint you run.
Every booking says who, what and when.
Each booking and cancellation arrives with the details a person needs, so a Zap can write a message or a spreadsheet row without looking anything up first. It also works the other way, for creating customers.
- The class and its start time. Every booking and cancellation names the class and when it starts, in the class's own time zone. A message can say "Saturday pasta class, 10am" instead of an id nobody reads.
- Who booked. The customer's name, email address and phone number (when they gave one) come with every booking, ready for a thank-you, a reminder or your CRM.
- Text reminders before class. Add a delay until the day before the class, then text the customer from your own SMS app, such as Twilio or ClickSend.
- Create a customer. An enquiry form, a waiting list or a tool you already use can open a FullClass customer record, ready for the first booking.
Related features
Send your bookings wherever you need them.
Connect Zapier and every new booking can update your spreadsheet, CRM or team chat.
30-day free trial · Cancel anytime