Integrations

Connecting Zapier

Zapier

Zapier connects FullClass to thousands of other apps, and nobody has to write code. A new booking can go into a Google Sheet, a new customer into your CRM, or a payment into your accounting app. Each connection is called a "Zap". Something happens in FullClass, then Zapier does something about it. You can set this up yourself, without a web person.

It uses the same webhooks described on the Webhooks page. So events reach Zapier within seconds, not on a timer, and you can see every delivery in your own log under Settings → Webhooks.

Connecting

  1. In FullClass, go to Settings → Integrations → Zapier. Only the account owner can open it. Press Open the Zapier invite. FullClass is in early access on Zapier, so you will not find it by searching Zapier's app list yet. The invite adds it to your Zapier account.
  2. Back on the same page, press Create a Zapier key. It opens Settings → API Keys, ready to create a secret key. It starts with sk_. A public key will not work. That is the key in your website, and it cannot read your bookings or customers. Only the account owner can open that page, because a secret key gives full access to the account. If the studio is not yours, ask the owner for the key.
  3. The form opens with Restricted chosen under Access and the Zapier preset ticked. Untick anything your Zaps will not use, then create the key. A restricted key lets Zapier read your bookings but not cancel or refund them or spend a gift card. If a Zap later says the key is missing a permission, create a new key with that box ticked and reconnect with it.
  4. Open the FullClass app in Zapier and paste the key when it asks. Once it connects, Zapier shows your studio name, so you can tell which account a Zap uses.
  5. Build your Zap. FullClass is the trigger (what starts the Zap), and the other app is the action.

Once a Zap is switched on, it appears under Settings → Integrations → Zapier, named by what starts it. Open one to see everything sent to it.

A full-access secret key can read and change everything in your account. Only paste it into Zapier itself. Never put it in a Zap step, an email or a shared document. If one leaks, revoke it under Settings → API Keys and create a new one.

What you can build on

Trigger Fires when
New Booking A booking is confirmed. A checkout someone gave up on does not count. A course booking fires once for each of its sessions.
Booking Canceled Anyone cancels. That can be the customer, a staff member, or a refund coming back from Stripe or Square.
Customer Checked In You check a customer in, by hand or by scanning their QR code. Checking the same person in again does not fire it twice. Good for a thank-you or a review request after class.
Booking Changed A booking moves to another class, or a staff member changes its payment or notes.
New Class Scheduled A class is added to your schedule, on its own, as part of a repeating series, or as a session of a course.
Class Changed A class gets a new time, location, instructor, price or size.
Class Canceled You cancel a whole class. Each booking on it also fires Booking Canceled.
New Customer A customer account is created for the first time. This can come from a booking, a staff member adding them, a spreadsheet import, a gift card purchase or someone signing up.
Payment Received Money is taken for a booking, a private event order, or a gift card or class pass sale.
Refund Issued Money goes back to a customer. This covers bookings (a refunded cancellation, a refund made in Stripe or Square, or a lost chargeback), gift card and class pass sales, and private events.
Waitlist Spot Offered A spot frees up in a class or course and is offered to someone on the waitlist.

For your accounting app. New Booking and Booking Canceled include the price, the discount, and each tax on its own line (GST and QST separately, for example). So a Zap can record the sale in QuickBooks or Xero with the tax split the same way as your tax report. Add Refund Issued so refunds reach your books too.

There is also one action, Create Customer. Zapier cannot create a booking. A booking takes a payment, and we will not let an automation charge someone's card.

Adding people to a mailing list? Read this one. The New Customer trigger has two consent fields, and they are not the same. Filter on Marketing Subscribed, which says whether you may email that person. Do not filter on Marketing Opt-In. That is only what they chose on the day their account was created. The two can differ even for a brand-new customer. If that email address unsubscribed from you before (perhaps as a gift card recipient, or under an older account), it still counts. Marketing Subscribed shows that, and Marketing Opt-In does not. If Marketing Subscribed is blank rather than true, treat it as unknown and leave that person out.

Zaps in your webhook list

Each Zap you switch on appears under Settings → Webhooks as a row marked Managed by Zapier. You did not create it and the address will not look familiar, which is why it is marked. Those rows have no Edit. Change them in Zapier, because an edit here would not reach Zapier.

Any other app connected through the FullClass API (by a developer, for example) appears the same way, marked Managed by a connected app. Only rows that send to Zapier are marked Managed by Zapier.

To stop a Zap, turn it off in Zapier rather than deleting the row here. Deleting it stops the events, but Zapier still thinks the Zap is connected and shows no error. It looks fine while receiving nothing. Delete it here only when you want to cut the connection from this side, for example if you no longer trust it.
← PreviousWebhooks
FullClass help center · Zapier