Keep your free/busy time in sync across multiple Google Calendars™ — without sharing event details.
Calendar Sync is a Google Workspace™ Add-on that helps users who work across multiple Google Accounts™ keep their availability consistent. It reads events from secondary calendars and creates private "Busy [calendar name]" blocks on your primary calendar automatically — without copying titles, descriptions, attendees, or any other event details.
Only the time slot is copied. Titles, descriptions, locations, and attendees are never shared.
An hourly trigger keeps calendars in sync with no manual action required.
Connect your work, personal, and client calendars — up to 2 source calendars.
Uses Google Calendar™ sync tokens so only changed events are processed each run.
Opens Google Workspace™ Marketplace
Open Calendar Sync on the Google Workspace™ Marketplace. Click Install and follow the prompts. Grant the requested permissions when asked. Open Google Calendar™ — a Calendar Sync panel appears in the right sidebar.
Before Calendar Sync can read a secondary calendar, that calendar must be shared with your primary Google Account™. Do this for each secondary calendar you want to sync:
you@gmail.com)
you@work.com)
Repeat for every additional secondary calendar before proceeding.
In the Calendar Sync panel, click Settings.
Calendar 1 is your primary calendar — it is pre-filled automatically with
your signed-in account. Under it, a dropdown lists all calendars currently shared with
your primary account. Select the secondary calendars you want to sync (e.g.
you@gmail.com, you@client.com). You can add up to
2 source calendars.
The sync window controls how far back and forward to create busy blocks.
Click Save & Start Sync. The add-on will run a full sync immediately, create "Busy [calendar name]" blocks on your primary calendar, and set up an hourly trigger to keep everything in sync automatically.
The block title uses the source calendar's display name when available, falling back to the email domain if no name is set.
| Event on secondary calendar | What appears on your primary calendar |
|---|---|
| "Team standup" (calendar named "Work") | Busy [Work] |
| "Doctor appointment" (calendar with no name set) | Busy [gmail.com] |
| All-day event | All-day "Busy" block |
| Cancelled event | Mirror removed |
| Rescheduled event | Mirror updated |
No titles, descriptions, locations, or attendees are ever copied — only the time slot.
| Action | What it does |
|---|---|
| Pause | Stops the hourly trigger (mirrors stay in place) |
| Resume | Restarts the hourly trigger |
| Full Resync | Deletes all mirrors and rebuilds from scratch |
| Stop & Clean Up | Deletes all mirrors and removes the trigger |
| Scope | User-facing feature and data used | Why a narrower scope is not viable |
|---|---|---|
| userinfo.email |
Setup form — primary calendar pre-fill. When the user opens Calendar Sync for the first time, the add-on calls Session.getActiveUser().getEmail() and pre-fills the
Calendar 1 (primary) field with the signed-in account's email. This ensures
mirror events are always written to the correct calendar.Data used: email address only. Not stored in user properties. Read once per card render and discarded. |
Without this scope, Calendar 1 is a blank editable field — the user could type any
email address, including one they do not own, causing mirrors to be written to
another person's calendar. No narrower scope returns the authenticated user's email
address. calendar.calendarlist.readonly returns calendar IDs but does
not identify which account is currently authenticated.
|
| calendar. |
Powers four features across setup and sync: Data used: calendar ID and display name only. Not stored beyond the duration of the sync run. |
No other scope exposes CalendarList metadata. Without it:
calendar.events.readonly returns event data only and does not include
calendar display names or access roles.
|
| calendar.events. |
Hourly sync — reading source calendars. On each sync run, Calendar.Events.list(srcId, params) is called for
each source calendar. The add-on reads:
This scope is used exclusively for reading. The add-on never writes
to source calendars.Data used: event IDs, start/end times, status, recurrence rules, extended properties. Event titles, descriptions, attendees, and locations are never read. |
calendar.events.freebusy targets the FreeBusy query
API (Freebusy.query), not the Events list API
(Events.list). It does not return event.id,
event.extendedProperties, event.recurrence,
event.recurringEventId, event.status, or
nextSyncToken — all of which are required for the sync engine to
correctly create, update, and delete mirror events.calendar.events (read + write on all calendars) was
considered but intentionally not requested. The add-on only reads from source
calendars — it never writes to them. calendar.events.readonly is the
narrowest scope that supports the Events list API with incremental sync tokens.
|
| calendar.events. |
Hourly sync and cleanup — reading and writing mirror events on the primary
calendar. All mirror events ("Busy [calendar name]" blocks) are created on and owned by the primary calendar. This scope is used for: Data written: start time, end time, recurrence rule, and three private/shared extended properties used to link the mirror to its source event. No event titles, descriptions, or attendees are written. |
calendar.events.readonly does not permit writes — mirrors could not be
created, updated, or deleted, making the core feature non-functional.calendar.events (read + write on
all calendars) was considered but intentionally not requested. Writing to
source calendars is never required — mirrors are always created on the primary
calendar, which the user owns. calendar.events.owned is the narrowest
scope that permits the required write operations and is strictly limited to events
the user owns.
|
| calendar. |
All UI interactions. Required by the Google Workspace™ Add-on platform to execute server-side card action callbacks when the user interacts with the sidebar. Every button in the add-on uses this scope: |
This scope is mandated by the Google Workspace™ Add-on platform for all add-ons that register card action callbacks. Without it, the Google infrastructure will not route button clicks back to the Apps Script handler functions. There is no narrower alternative — it is a platform requirement, not a data access request. |
| script.scriptapp |
Automatic background sync. Used exclusively to create and delete Apps Script time-based triggers: |
No narrower scope exists in the Google Apps Script™ platform for creating or deleting time-based triggers. Without it, the add-on has no way to run automatically — the user would need to open the sidebar and click Run Now manually every time they want calendars updated. Background operations (initial sync after setup, cleanup after stop) would also be impossible, as there is no other mechanism to execute a function outside of a direct user interaction. |
Calendar Sync is a free Google Workspace™ Add-on that helps users synchronize busy time across multiple Google Calendar™ accounts. The add-on creates generic "Busy" calendar blocks so that availability from one configured calendar can be reflected in another calendar without copying the details of the original event.
Calendar Sync accesses only the Google user data required to provide its synchronization functionality:
Calendar Sync does not access, use, or store the titles, descriptions, attendee information, conference details, or locations of existing calendar events. Event content is never read or transmitted — only timing information is processed.
User data obtained from Google APIs is used solely to provide the calendar synchronization functionality requested by the user:
User data is not used for advertising, profiling, marketing, analytics, AI/ML model training, or any purpose unrelated to calendar synchronization.
Calendar Sync does not use artificial intelligence or machine learning systems of any kind. User data obtained from Google Workspace™ APIs is not used to develop, improve, or train any AI or machine learning model — whether operated by the developer or by any third party. No user data is transferred to any AI or machine learning service.
Calendar Sync does not operate an external application server or database. The only data stored by the add-on is the user's own configuration (calendar email addresses, sync window settings, and sync state tokens), which is stored exclusively in Google Apps Script™ User Properties — a per-user, per-script storage mechanism provided by Google that is not accessible to other scripts or third parties.
Calendar event data is processed transiently within Google's Apps Script™ runtime. No calendar content is written to or cached in any external storage controlled by the developer.
Access to Google Calendar™ data is protected by Google's OAuth 2.0 authorization system. Users explicitly grant and can revoke permissions at any time via their Google Account™ security settings. The add-on requests only the minimum OAuth scopes necessary to function (see the Permissions section).
Configuration data stored by Calendar Sync is retained only as long as the user keeps the add-on installed and configured.
Calendar Sync does not use any third-party analytics, advertising, tracking, telemetry, or data-processing services. The add-on operates exclusively within Google's infrastructure using Google Workspace™, Google Calendar™ APIs, and Google Apps Script™.
Calendar Sync's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide the user-facing calendar synchronization functionality of Calendar Sync.
For questions about this Privacy Policy or Calendar Sync's handling of user data, contact: lucamit@gmail.com
By installing, accessing, or using Calendar Sync, you agree to these Terms of Service. If you do not agree to these terms, you should not install or use the add-on.
Calendar Sync is a Google Workspace™ Add-on that helps synchronize busy time between configured Google Calendar™ accounts. The add-on may create, update, and remove generic "Busy" calendar blocks based on the availability of configured calendars. Calendar Sync is intended to assist with availability synchronization only and should not be relied upon as the sole source of important scheduling information.
Calendar Sync is currently provided free of charge. There are no subscription fees or paid features at this time. The developer reserves the right to introduce paid features, modify pricing, or discontinue free access in the future. Where reasonably possible, users will be informed before such changes take effect.
Calendar Sync is provided "as is" and "as available" without warranties of any kind, whether express or implied. The developer does not guarantee that:
Users should independently verify important appointments, meetings, and scheduling information.
To the maximum extent permitted by applicable law, the developer will not be liable for any direct, indirect, incidental, special, consequential, or similar damages arising from the use of, or inability to use, Calendar Sync. This includes, without limitation:
Use of Calendar Sync is at your own risk.
By using Calendar Sync, you agree that:
Calendar Sync depends on services provided by Google, including Google Calendar™, Google Workspace™ APIs, Google Apps Script™, and Google's authentication infrastructure. Availability or functionality of Calendar Sync may be affected by changes, outages, restrictions, rate limits, or discontinued functionality within Google's services. The developer is not responsible for interruptions or changes caused by Google's services.
See the Setup Guide above for configuration and usage guidance.
Email lucamit@gmail.com and please include: