C
Integration // Google Calendar

Your week,
handled — and double-booking-proof.

Connect Google Calendar and Ledger can tell you what's booked, draft new appointments from a conversation, and check for a real time conflict before anything gets saved — not a best guess.

How it works
1

Ledger reads your schedule

Ask what's booked today, tomorrow, or next week and Ledger pulls it straight from Google Calendar — times shown correctly in your business's timezone.

2

It drafts the booking, you confirm it

Tell it who, what, and when — Ledger builds the appointment and shows you the draft before touching your calendar. Nothing is created without your tap.

3

It checks for a real conflict — not a guess

Before confirming, Ledger looks at what's actually on the calendar in that window. If the time overlaps an existing appointment, it tells you exactly what it collides with — the other appointment's name and time — instead of quietly double-booking you.

4

You can override it — on purpose

Sometimes a double-booking is intentional — two techs, one bay. Ledger blocks it by default but lets you push through deliberately when you actually mean to.

What Ledger can do with it

A scheduler that checks its own work

"What's on my schedule?" answered instantly, for today, a specific day, or a date range.

AI-drafted bookings from a plain-language request — Ledger fills in the appointment details and waits for your confirm.

Live conflict detection on every booking — it checks the actual calendar window, not an assumption, and names the appointment it collides with.

Deliberate override when you genuinely want to double-book — the block is a default, not a wall.

Timezone-correct, always — appointment times display in your business's actual timezone, not wherever the server happens to run.

Edit and cancel — booked something wrong or need to move a slot, Ledger updates the calendar event directly.

— Your data

Google Calendar access is read-and-create: Ledger can see what's booked and add appointments you ask it to schedule. It does not touch events it didn't create except when you explicitly ask it to edit or cancel one.

The connection uses Google's standard OAuth consent — you approve the exact scopes on Google's own screen, and can revoke access from Google or from Ledger's Settings → Connections at any time.

See the Privacy Policy for full details on what's stored and how to delete it.

Never double-book again

Connect Google Calendar and let Ledger check its own work before it saves anything.

Open Ledger AI →