SchedulingKit
Integrations
Via ZapierAutomation

SchedulingKit triggers, actions and webhook workflows in Zapier

SchedulingKit has a public Zapier app with booking triggers, actions and searches. You build the Zap: choose a SchedulingKit trigger, then the action in the other app, and map the fields. For events the app doesn't cover, send a SchedulingKit webhook to Zapier's Catch Hook trigger.

Connects through Zapier

Zapier is where you build the workflow. SchedulingKit supplies triggers (New Booking, Booking Cancelled, Booking Rescheduled, New Customer), actions (Create Booking, Cancel Booking) and searches (Find Booking, Find Customer). Zapier connections use SchedulingKit's API and webhooks, which are included on the Pro plan and above. You also need a Zapier account, and each Zap runs on your Zapier plan.

Known issue: signing in to the SchedulingKit app inside Zapier with an API token currently fails. Until that’s fixed, add a webhook in SchedulingKit (Settings → Webhooks, Pro plan and above) that points to a Webhooks by Zapier “Catch Hook” trigger. See API & webhooks

Features

New Booking trigger
Booking Cancelled trigger
Booking Rescheduled trigger
New Customer trigger
Create Booking and Cancel Booking actions
Find Booking and Find Customer searches
Webhook route for other events

Why Connect Zapier?

Connect bookings to apps SchedulingKit doesn't integrate with directly

You decide exactly which fields go where

Webhooks cover events the Zapier app doesn't, such as completed appointments and payments

How It Works

01

Check your plan

Zapier workflows need SchedulingKit's API and webhooks, included on Pro and above.

02

Choose a trigger

In Zapier, pick a SchedulingKit trigger, or Webhooks by Zapier → Catch Hook if you're using a SchedulingKit webhook.

03

Add the action

Choose the app and action to run, and map SchedulingKit's fields to it.

04

Test and turn on

Make a real test booking on your booking page, check the result, then turn the Zap on.

Zapier workflows

Bookings to your CRM

Use New Booking as the trigger and your CRM's create-or-update contact action. Map the client's email (as the matching key), name and phone, and optionally the service name and booking time to custom fields. The same pattern works for HubSpot, Salesforce, Pipedrive and ActiveCampaign.

Adding clients to an email list

Use New Booking and your email tool's add-or-update subscriber action. Pick the list or audience and tags explicitly, and only subscribe clients who've agreed to marketing email. A booking isn't consent to marketing.

Invoices after appointments

There's no packaged “appointment completed” trigger. Either create the invoice from New Booking, or send SchedulingKit's event.updated webhook to a Catch Hook and add a Zapier filter for status = completed. Check whether the booking was already paid online so you don't bill twice.

Lead capture

New Booking gives you the client's name, email and phone plus the service booked. Map those to the lead or contact record in your destination app. New Booking includes the booking ID, service name and ID, client name, email and phone, start and end time, time zone, status, notes, location, meeting link and payment amount. It does not include the assigned staff member.

What the Zapier integration doesn't do

  • No packaged triggers for completed appointments, payments, reminders or client inactivity. Use webhooks for completed/no-show status and payments.
  • The New Booking trigger fires for bookings made on your booking page or through the API. Bookings you add by hand in the SchedulingKit dashboard don't fire it.
  • New Customer fires for clients you add in the dashboard or through the API, not for clients created automatically by a booking.
  • The Create Booking action doesn't take payments.
  • Zapier connections use SchedulingKit's API and webhooks, which are included on the Pro plan and above. You also need a Zapier account, and each Zap runs on your Zapier plan.

Frequently Asked Questions

Technical Details

Connection

SchedulingKit's public Zapier app, or SchedulingKit webhooks sent to Webhooks by Zapier.

Data available

Booking ID, service, client name/email/phone, start/end, time zone, status, notes, location, meeting link, payment amount. No staff field.

Plan

Pro and above, plus a Zapier account.

Further Reading

Ready to Get Started?

Join 5,000+ teams using SchedulingKit

Free forever plan available • No credit card required