SchedulingKit
Integrations
Via ZapierProductivity

Connect SchedulingKit to Notion via Zapier

There's no native Notion connector. With Zapier, each new booking can become an item in a Notion database with the client, service and time. Anything richer, like client pages with full history or project progress, is something you build and maintain in your Zaps.

Connects through Zapier

There's no native Notion connector. You build a Zap: SchedulingKit's New Booking trigger, then Notion's create-item action on a database you choose. 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 → Notion database item
Map client, service, time and status
Booking ID property to avoid duplicates
Separate Zaps for cancellations and reschedules

Why Connect Notion?

See upcoming appointments alongside your notes and projects

Filter and sort bookings with Notion views

Keep a booking log without copy-pasting

How It Works

01

Prepare the database

Create a Notion database with properties for client, email, service, start time, status and a Booking ID.

02

Trigger

In Zapier, choose SchedulingKit → New Booking.

03

Action

Choose Notion's create-item action on that database and map the fields, including Booking ID.

04

Handle changes

Add Zaps for Booking Cancelled and Booking Rescheduled that find the item by Booking ID and update it.

Notion workflows

A booking database

Store the SchedulingKit booking ID in its own property. Your cancellation and reschedule Zaps can then find the right item and update its status or time instead of creating duplicates.

Client pages

A Zap can create a basic page per client from New Booking. Keeping a full client history or notes on that page needs extra Zap steps to find the existing page and append to it; SchedulingKit doesn't maintain it for you.

Linking bookings to projects

If you track projects in Notion, you can relate a booking item to a project by adding a lookup step to your Zap (for example, by client email). SchedulingKit doesn't know about your projects, so milestones and progress aren't updated automatically.

What the Notion integration doesn't do

  • No native Notion app and no two-way sync.
  • Client history, notes and project progress aren't maintained automatically.
  • Cancellations and reschedules need their own Zaps.
  • 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.
  • 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

Zapier: SchedulingKit trigger → Notion action.

Direction

One way, SchedulingKit to Notion.

Plan

SchedulingKit Pro and above, plus Zapier.

Further Reading

Ready to Get Started?

Join 5,000+ teams using SchedulingKit

Free forever plan available • No credit card required