Google Calendar's appointment schedule is the booking page that comes with your Google account. You set the hours and the length, Google makes a page, strangers pick a slot, and the event lands on your calendar with a Meet link and the guest's answers. It replaced the older appointment slots feature in July 2024, and if you are on Workspace you have probably clicked past it a hundred times under the Create button.
I spent an afternoon in October 2026 trying to wire one into a CRM for a brokerage that pays for a scheduling seat per adviser, and I hit the same three walls everyone hits. This page is the walls, what each account type gets, and the way round each one. The working version, with code, is in the recipe.
What you get, by account
Google's own comparison page is a chart, so here it is as a table, read on 12 October 2026.
| Personal account, Business Starter | Google One Premium | Workspace Individual | Business Standard and above | |
|---|---|---|---|---|
| Booking pages per person | One | Several | Several | Several |
| Automatic email reminders | No | Yes | Yes | Yes |
| Check more than one calendar for clashes | No | Yes | Yes | Yes |
| Email verification for guests | No | No | Yes | Yes |
| Paid bookings through Stripe | No | No | Yes | Yes |
| Up to 20 co-hosts | No | No | No | Yes |
| Schedule on a secondary calendar | No | No | No | Yes |
Workspace Frontline, Essentials and the older subscriptions Google no longer sells cannot create one at all. Business Starter is the trap for small businesses: one page per person means one meeting type per person, so a ten-minute chat and a forty-minute conversation is already an upgrade to Standard, which Google prices per user per month and which the brokerage was going to pay anyway for the reminders.
Everything else is the same on every tier. Custom booking form questions, a buffer between appointments, a minimum notice period, a cap on bookings per day, Meet links, and the invite with its reschedule and cancel links.
The three walls
Each of these is a thing Calendly, Acuity and the rest do for you, and each is the reason people conclude Google's page cannot be used for real work.
No webhook
Calendly posts every booking to a URL you give it. Google's booking page tells nobody anything. There is no setting, no "notify this address", no Zapier trigger called "new booking".
The way round it is to stop watching the page and watch the calendar, because the event is the one thing Google reliably produces. Three ways to do that, in order of effort:
In your own Google account, a Google Apps Script can register a trigger that fires the moment any event on the calendar changes. No server, no certificate, no cost. The script asks the Calendar API what changed since it last looked, using a sync token, so it never re-reads the whole calendar. On my own site that path moved a CRM record two seconds after the booking.
From outside Google, the Calendar API has push notifications: you call events.watch with an HTTPS address and Google posts to it on every change. The notification carries no detail about what changed, so you still fetch the changes, Google says plainly that they are "not 100% reliable", and the channel expires and does not renew itself, so you run a second one before the first one dies. It works, and it is more plumbing than the Apps Script route for the same result.
Through Zapier, Make or n8n, the Google Calendar node reads the calendar on a schedule your plan sets, and the same "has an outside guest, not seen before" rule turns an event into a booking. Slower than a trigger, fine for a sales team.
No redirect
After booking, Calendly can send the visitor to a page of yours. That page fires the conversion pixel and knows which ad the visitor came from. Google's page shows its own confirmation and stops, and nothing you own ever sees the visitor again.
The way round it is to capture before the page, not after. Put a short form of your own in front of the booking page: name, email, what the call is about. Your page has already read the UTMs and the click ids from the address bar, so the record exists, with its source, before the visitor has picked a slot. Then show Google's page in a frame on the same URL. The conversion fires from the calendar watcher instead of from a thank-you page, which is slower by a minute and better in every other way: it survives ad blockers, it fires once, and the Google click id is already on the record for offline conversion uploads.
No prefill
Calendly links accept the visitor's name and email in the URL, so a link from an email lands them on a form already filled in. Google's booking page starts blank every time, and the embed URL ignores anything you append to it.
There is no way round this one, only a choice. Accept that the visitor types their name and email twice, once on your form and once on Google's, and measure how many drop out between the two. Or build your own slot picker on the Calendar API, which reads free and busy times and inserts the event itself. That is a few days of work for a developer and it removes Google's page entirely, so at that point you are writing a scheduler, and the free one you were trying to use is gone.
What the walls are protecting
None of this is an oversight. Google does not sell a scheduler. The booking page is a feature of Calendar, the way the Meet link is, and features of Calendar do not get a developer surface of their own. Everything that happens on the page ends up as an event, and events already have the whole Calendar API behind them. From Google's side the webhook exists; it is just on the calendar, not on the page.
That is also why the free page keeps being free. The scheduling companies charge per seat for the redirect, the prefill and the webhook, and Google would rather you paid for Workspace Standard than for any of them.
Who has done it natively
The only CRM I found that treats a Google booking as a lead without any of this is Kommo, which watches your main Google calendar and drops each booking into the first stage of its pipeline. Main calendar only, one page per free account, and its documentation says nothing about where the lead came from. Capsule's marketplace has a Calendly integration and nothing for Google. HubSpot, Pipedrive and the rest sell their own meeting links, which is the webhook and the prefill sold back to you at the CRM's price.
The recipe
Capture first, then book, then watch the calendar. One Google Apps Script for a single person, two n8n workflows for a team, a plain booking page, the Capsule schema and a lesson plan, all in a public repository under an MIT licence, and the reasoning, the losses and the timings in the article that goes with it.
Sources: Google Calendar Help, "Learn about appointment schedules", "Create an appointment schedule" and "Compare premium features for appointment schedules"; the Google Workspace Updates blog, March 2024, on the move from appointment slots to appointment schedules; the Google Calendar API guides to push notifications and to synchronising resources efficiently; Google Apps Script's documentation on installable calendar triggers; Kommo's Google Calendar integration guide; Capsule's integration marketplace. All read 12 October 2026.