DiscoveryVIP / Apps Script AcademyHelp

51. Calendars and events

Module 11 · 20 minutes · Lesson 50; earlier service and JavaScript fundamentals

Open Interactive Lesson

Discover

How can you use calendars and events without changing the wrong data?

Predict

Which values or resources will change, and which should stay unchanged? Write your prediction before execution.

Understand

A Calendar contains events with start and end timestamps. getDefaultCalendar uses the executing account’s default in Google. The simulator uses a fictional primary calendar. Event creation can notify people if guests or notification options are supplied; this course’s sample exports omit guests. Check the destination calendar and interval before creating anything.

Example 1: Working automation

The end follows the start by one hour. Reversing it is rejected before recording an event.

function main() {
  const calendar = CalendarApp.getDefaultCalendar();
  calendar.createEvent("Study session", new Date("2026-12-01T14:00:00Z"), new Date("2026-12-01T15:00:00Z"));
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: const calendar = CalendarApp.getDefaultCalendar();
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: calendar.createEvent("Study session", new Date("2026-12-01T14:00:00Z"), new Date("2026-12-01T15:00:00Z"));
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [],
  "error": null,
  "resource": "calendars",
  "value": {
    "primary": [
      {
        "id": "event-1",
        "title": "Study session",
        "start": "2026-12-01T14:00:00.000Z",
        "end": "2026-12-01T15:00:00.000Z"
      }
    ]
  }
}

Example 2: Investigate a reproducible failure

Predict the effect of 13:00:00Z and identify the first mismatch. This example is intentionally faulty.

function main() {
  const calendar = CalendarApp.getDefaultCalendar();
  calendar.createEvent("Study session", new Date("2026-12-01T14:00:00Z"), new Date("2026-12-01T13:00:00Z"));
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: const calendar = CalendarApp.getDefaultCalendar();
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: calendar.createEvent("Study session", new Date("2026-12-01T14:00:00Z"), new Date("2026-12-01T13:00:00Z"));
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [],
  "error": "Calendar end must be after start.",
  "resource": "calendars",
  "value": {
    "primary": []
  }
}

Example 3: Separate setup from execution and inspect repeat behavior

Call the same named operation twice. Compare outputs and resource counts to learn whether this operation is idempotent. Repeated creation is deliberately visible; real exports require a rerun policy.

function lessonAction() {
  const calendar = CalendarApp.getDefaultCalendar();
  calendar.createEvent("Study session", new Date("2026-12-01T14:00:00Z"), new Date("2026-12-01T15:00:00Z"));
}
function main() {
  lessonAction();
  lessonAction();
}
Important line explanations
Line 1: function lessonAction() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: const calendar = CalendarApp.getDefaultCalendar();
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: calendar.createEvent("Study session", new Date("2026-12-01T14:00:00Z"), new Date("2026-12-01T15:00:00Z"));
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 5: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 6: lessonAction();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 7: lessonAction();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 8: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [],
  "error": null,
  "resource": "calendars",
  "value": {
    "primary": [
      {
        "id": "event-1",
        "title": "Study session",
        "start": "2026-12-01T14:00:00.000Z",
        "end": "2026-12-01T15:00:00.000Z"
      },
      {
        "id": "event-2",
        "title": "Study session",
        "start": "2026-12-01T14:00:00.000Z",
        "end": "2026-12-01T15:00:00.000Z"
      }
    ]
  }
}

Example 4: Add a diagnostic boundary around the operation

Observe start, successful completion or a rethrown failure. This optional professional pattern adds error context without swallowing the error or rolling back changes.

function lessonAction() {
  const calendar = CalendarApp.getDefaultCalendar();
  calendar.createEvent("Study session", new Date("2026-12-01T14:00:00Z"), new Date("2026-12-01T15:00:00Z"));
}
function main() {
  console.log("Start: Calendars and events");
  try { lessonAction(); console.log("Completed operation"); }
  catch(error) { console.error("Failed operation: " + error.message); throw error; }
}
Important line explanations
Line 1: function lessonAction() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: const calendar = CalendarApp.getDefaultCalendar();
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: calendar.createEvent("Study session", new Date("2026-12-01T14:00:00Z"), new Date("2026-12-01T15:00:00Z"));
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 5: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 6: console.log("Start: Calendars and events");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 7: try { lessonAction(); console.log("Completed operation"); }
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 8: catch(error) { console.error("Failed operation: " + error.message); throw error; }
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 9: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Start: Calendars and events",
    "Completed operation"
  ],
  "error": null,
  "resource": "calendars",
  "value": {
    "primary": [
      {
        "id": "event-1",
        "title": "Study session",
        "start": "2026-12-01T14:00:00.000Z",
        "end": "2026-12-01T15:00:00.000Z"
      }
    ]
  }
}

Build and test

Repair the supplied script so that: The end follows the start by one hour. Reversing it is rejected before recording an event. Preserve other source data. Checks compare observable output and the named resource, not exact source text.

function main() {
  const calendar = CalendarApp.getDefaultCalendar();
  calendar.createEvent("Study session", new Date("2026-12-01T14:00:00Z"), new Date("2026-12-01T13:00:00Z"));
}

Graduated hints

Hint 1

Inspect the operation containing 13:00:00Z. Compare it with the stated rule and the first mismatch.

Hint 2

The repair concerns 15:00:00Z. Change only the relevant argument, operator or method; rerun with fresh input.

Hint 3

The reference uses 15:00:00Z where the broken source uses 13:00:00Z. Explain why before applying it.

Reference solution

function main() {
  const calendar = CalendarApp.getDefaultCalendar();
  calendar.createEvent("Study session", new Date("2026-12-01T14:00:00Z"), new Date("2026-12-01T15:00:00Z"));
}

Explain and reflect

Which operation proves the intended result in calendars and events? Which wrong input would expose a weakness, and what would remain unchanged?

Adapt the input records and calendars output to a second realistic case. Write its expected result before running. Demonstrate one invalid case and explain whether the side effects should be rolled back or retried.

Troubleshooting

If the console is empty, inspect the calendars preview: this script may work through state changes. If the function is missing, select main. For a service error inspect the first failed timeline entry and its arguments. Use Manual unless investigating a trigger. Changing input data also changes the expected result; restore sample data before the authored checks.

Knowledge check

Explain the key method or operator. Give an exact output for a second input, plus one invalid case. Verify the result in the interactive lesson; written explanations need self or educator review.

Optional AI practice

Explain this concept using the source above. Help implement one small extension and define its tests. Review/debug the source using its actual expected output; cite real method references and never claim execution.

Transfer to Google and authorization guide

Next lesson: Reading and searching events