TeamSchedulerPro

Connect TeamSchedulerPro to Zapier

Send every new (or cancelled) booking into 5,000+ apps — Slack, Google Sheets, your CRM, Mailchimp, and more — using your webhook and Zapier's built-in Webhooks by Zapier trigger. No code, about 10 minutes.

How it works: TeamSchedulerPro fires a webhook the instant a booking is created or cancelled. Zapier gives you a unique URL that "catches" that webhook; you then map the fields to any action you like. You'll set this up in two browser tabs — Zapier in one, your TeamSchedulerPro Developers panel in the other.

1

Start a Zap with a "Catch Hook" trigger

In Zapier, click Create → Zap. For the Trigger, search for and choose Webhooks by Zapier, then pick the Catch Hook event and continue.

Zapier shows you a Custom Webhook URL that looks like:

https://hooks.zapier.com/hooks/catch/123456/abcde/

Copy it. Leave this Zapier tab open.

2

Paste it into TeamSchedulerPro

In your admin dashboard, open the Developers panel → Webhooks. Paste the Zapier URL, tick the events you want (booking.created, booking.cancelled, or both), and click Add webhook.

3

Send a test so Zapier learns the fields

Next to the webhook you just added, click Test. That fires a sample delivery to Zapier. Back in the Zapier tab, click Test trigger — you should see the sample booking appear. Now Zapier knows every field it can use:

FieldExample
data__clientNameJane Doe
data__clientEmailjane@example.com
data__meetingTypeIntro Call
data__date / data__time2026-06-10 / 14:00
data__timezoneAmerica/New_York
data__videoLinkhttps://zoom.us/j/…
eventbooking.created

Want richer sample data? Create one real test booking on your booking page — Zapier will pick up that payload too.

4

Add your action

Add an Action step for whatever you want to happen, and map the fields from step 3. A few popular recipes:

  • Slack — post "New booking: {{clientName}} — {{meetingType}} on {{date}}" to a channel.
  • Google Sheets — add a row for every booking.
  • Mailchimp / CRM — add or update the contact using clientEmail and clientName.
  • Filter first — add a Filter by Zapier step (e.g. only continue when event is booking.created) if a single Zap handles both events.
5

Turn it on

Click Publish in Zapier. That's it — every matching booking now flows straight into your other tools, in real time.

Keep the Zapier URL private. Anyone with it can post events to your Zap, so treat it like a secret. If it ever leaks, delete the webhook in the Developers panel and generate a fresh Catch Hook URL in Zapier. (Zapier doesn't check our X-TSP-Signature header, but the secret URL is what protects the connection.)

Prefer a deeper integration? The same data is available over our REST API & webhooks, which you can build against directly. Questions? Email support@teamschedulerpro.com.

Open the Developers panel →