For teams and individuals who plan in spreadsheets: each row becomes a calendar event with its date, time, guests and description, and when an event is moved in the calendar or a row is edited in the sheet, the other side follows.
I need thisEarly access · No payment is taken on this page yet
A training company schedules 120 sessions a term in a Google Sheet: trainer, room, date and time. One run turns them into events in the trainers' calendars with the room in the location field. When a trainer moves a session in the calendar, the next daily sync updates its row, and the office sees the change in the sheet without asking.
Choose your planMany schedules start in a spreadsheet: shifts, classes and training sessions, content calendars, project deadlines, rentals, maintenance visits. A sheet is easy to fill, sort and share. But people look at their calendar, not at the sheet, so the same dates are often typed in twice.
Copying rows into the calendar by hand works for ten events, not for a hundred. And once the events are there, the two copies drift apart: someone moves a meeting in the calendar, someone else edits the date in the sheet, and nobody is sure which version is right.
The add-on connects a Google Sheet with one or more Google Calendars. You map the columns once: which column holds the title, the start and end date and time, the location, the guests and the description. Then one run creates an event for every row.
Each row stays linked to its event through a hidden column, so the link survives sorting and filtering. When you edit a row and sync again, the event is updated; when you delete the row, you can choose whether the event is deleted too.
The link works in the other direction as well. Events changed in Google Calendar — moved to another day, renamed, given a new location — are brought back into their rows. Events for a date range can also be imported into a new sheet, which is handy for reports on time spent or for checking who was booked when.
Sync can run on demand or automatically once a day. Each run first brings changes from the calendar into the sheet and then sends the rows that no longer match back to the calendar, so both sides end up the same.
Teams on Google Workspace can use one sheet to fill several calendars, for example one calendar per trainer, room or vehicle, chosen by a column in the row.
The add-on runs inside Google Sheets for individuals and teams in any country; nothing needs to be installed on a computer.
Before a large run, a preview shows how many events will be created, changed or deleted in each calendar, so a wrong column mapping is caught before anything changes. Every run is logged in the sheet with the time and the number of events touched, and rows that could not be synced are marked with the reason, such as a missing date or an end time before the start.
Recurring work fits the same pattern: a weekly class, a monthly maintenance visit or a shift rota can be written as rows and kept in step with the calendar for the whole term or season.
The service is in preparation: we are checking whether Google Sheets users need it before it is built.
The add-on changes only the calendars you connect and the rows you map. Keeping the schedule itself correct stays with the owner of the sheet.
People and teams who plan in Google Sheets and want the same dates as events in Google Calendar.
Yes. Changes in the sheet go to the calendar, and changes in the calendar come back to the sheet.
Yes, once a day, or any time you start it by hand.
Yes. A column in each row can choose the calendar for that event.
Not yet. The service is in preparation, and we are checking whether Google Sheets users need it.