Calendly connects to Google Calendar, Outlook or Office 365, or iCloud, reads events from every calendar you connect to figure out your real availability, and writes each new booking back to whichever calendar you set as the default for that event type. You can connect several calendars just to check for conflicts while still writing confirmed bookings to one place. Time zones convert automatically based on where Calendly detects the invitee is booking from.
Conflict checking across multiple calendars. Connect a work calendar and a personal one, and Calendly blocks a slot if either shows a conflict, even though bookings only ever get written to your chosen default calendar.
One default calendar per event type. Different event types can write to different calendars, useful if, say, sales calls and internal 1:1s should land on separate calendars, but each event type still only writes to one.
Only three calendar providers. Google, Outlook/Office 365, and iCloud cover a lot of individual users, but a business running its scheduling through a practice-management system, a field-service dispatch board, or a shared resource-booking tool that isn't one of those three has nothing native to connect to.
No merging, just checking and writing. Calendly never combines your calendars into one shared view anywhere outside its own interface. It just reads from what you've connected and writes bookings to one spot.
The gap shows up for any business whose real scheduling system of record isn't Google, Outlook, or iCloud. A field service company tracking technician availability in a dispatch tool, or a clinic running a separate practice-management calendar, has no native way to keep that system and Calendly's idea of availability in sync. The usual workaround is exporting an .ics file by hand, or just not syncing at all and hoping two people don't try to grab the same slot from two different systems.
The same gap runs the other way too: a booking confirmed in Calendly needs to show up on a shared team calendar, a dispatch board, or a resource scheduler that Calendly has never heard of, and nothing native carries it there.
A field tech's real schedule, tracked in a dispatch or job-management tool rather than Google or Outlook, feeds into Calendly's availability so it never offers a slot that's already booked somewhere else.
A new Calendly booking shows up automatically on a shared team calendar, dispatch board, or resource scheduler outside Calendly's three supported providers, instead of someone copying it over by hand.
Tell us what it is, and whether Calendly already knows it exists.
Three supported providers cover plenty of individual schedules and not much else once a business's real availability lives somewhere else, a dispatch tool, a practice-management system, a shared resource calendar. We build the bridge for whichever system that actually is, and Calendly's sync is just one example of this. The same question is worth asking about any calendar your business runs that isn't Google, Outlook, or iCloud.
Let's talk →Google Calendar, Outlook or Office 365, and iCloud. Those three cover reading availability and writing new bookings. Anything else needs a custom connection built on top of Calendly's API.
Yes. Connect several calendars and Calendly checks all of them before offering a time slot, even though a given event type still writes confirmed bookings to only one calendar you've chosen as its default.
Yes. Calendly detects the time zone of whoever's viewing the booking page and displays available slots in their local time, converting everything back to your own calendar's time zone once it's booked.
Calendar sync has a short delay, so a cancellation or reschedule in Calendly can take a minute or two to clear the old event from a connected calendar. If it persists longer than that, check that the calendar connection itself is still active in Calendly's settings.