In this project, I created a service file where I put most of the functions related to retrieving or handling Calendar data. I did this just to help me organize my code a little better.

In this example, I use the getAllOwnedCalendars() method instead of getAllCalendars(). If you wanted to get all the calendars that the user has access to, you would use the latter. This will return an array of the user's calendars. In this case, I wanted to get the name of each calendar so I use the map method to get the name of each calendar in that array. I then display each calendar name as an option in a select input in the sidebar:

(function getCals () {
  google.script.run.withSuccessHandler(
    function (selectList) {
      var select = document.getElementById("calendar_name");
      for (var i=0; i<selectList.length; i++) {
        var option = document.createElement("option");
        option.text = selectList[i];
        select.add(option);
      }
    }
  ).getUserCalendars();
}());

In this example, I use the As you can see, I use the parameter form_data. This is the client-side data captured in a form that is displayed in an HTML sidebar. (See this link for more information on building side-bars and other HTML content.)

The calendar ID can be found in the settings page of any Google Calendar. This function will return the ID as a string. This is useful since the getCalendarById(id) method requires a string as the ID parameter.

There are many things you can do with the Calendar service. See the reference doc for more information. In this project, I only show how to create an event. You should be able to use these same principles to do anything else with this service.

First, notice that there are multiple event types: all day events, all day event series, events, and event series. (There is technically another type - createEventFromDescription(description). We will not talk about it in this project though.) I'm going to assume that you are already familiar with these event types from an end-user perspective. From the developer perspective, the difference in these event types are the required parameters. For all event types, a title is always required as well as some sort of start date or time. In addition, all day events require a start date (time is ignored) and regular events require and start date/time and an end date/time.

Each event type can also include an options class as a parameter. This is where we see one of the main differences between using the Workspace services and the advanced services. The options for the Workspace services are limited to description, location, guests, and sendInvites. The advanced services has many more options. See the reference doc for the full list.