How much does zuzu.codes cost?

The starter track is free — read all lessons and practice for free. Full access to every track (current and future) is $14.99/month. Cancel anytime.

How long does each track take?

Each track is designed as a 30-day challenge — one lesson per day, about 15 minutes each. Go at your own pace, but the structure is built around daily consistency.

What's the lesson format?

Each lesson is a student-teacher dialogue with code examples, followed by a hands-on code challenge in an in-browser editor. You read, you understand, then you write real code.

Do I need prior coding experience?

Our beginner track starts from absolute zero — no prior experience needed. Advanced tracks build on earlier ones, and the platform tells you exactly where to start.

How is zuzu.codes different from freeCodeCamp or Codecademy?

zuzu.codes uses a structured 30-day track format with dialogue-based teaching, an in-browser code editor, and gamification (XP, streaks, progress tracking). The format builds genuine understanding through daily practice.

Calendar to Sheet: Logging Events with Nested Fields — Automation For Beginners

Day 26 · ~12 min●

Events carry more structure than emails — a title lives under one key, a start time lives in a nested dict. What's the clean way to pull both into one row?

Read summary off the event for the title, reach into start.dateTime for the timestamp, then pass both as one row to the append call?

Exactly. event.get("start", {}) first to grab the nested dict safely, then .get("dateTime", "") for the string. Two layers, two defaults, no crashes:

python

events = toolset.execute_action(Action.GOOGLECALENDAR_FIND_EVENT, {"query": query})
items = events.get("items", [])
for event in items:
    title = event.get("summary", "")
    start = event.get("start", {}).get("dateTime", "")

.get("start", {}).get("dateTime", "") chained — if start is missing, the {} default keeps the second .get safe?

Exactly. An empty dict still supports .get, so the second call returns "". Your row always has two strings in it regardless of what shape the event carries:

python

def calendar_to_sheet(query: str, spreadsheet_id: str) -> int:
    events = toolset.execute_action(Action.GOOGLECALENDAR_FIND_EVENT, {"query": query})
    items = events.get("items", [])
    count = 0
    for event in items:
        title = event.get("summary", "")
        start = event.get("start", {}).get("dateTime", "")
        toolset.execute_action(Action.GOOGLESHEETS_SPREADSHEETS_VALUES_APPEND, {
            "spreadsheetId": spreadsheet_id, "range": "Sheet1",
            "values": [[title, start]], "valueInputOption": "USER_ENTERED",
        })
        count += 1
    return count

What if an event has no summary — is an empty title useful or should I skip it?

Depends on the downstream use. Appending a blank cell keeps row alignment so column 1 is always "title"; skipping keeps the log tidy but breaks positional analysis. For a growing log, keep everything and filter later.

So every matching event becomes a row — title column, timestamp column — ready for pivots or charts?

That is the payoff of a structured log. A pivot table on two clean columns beats a scroll through a calendar every time.

Nested .get() Chains

TL;DR: Reach into nested dicts with .get(key, {}) before the next .get — every layer defaults.

Events — summary is the title, start.dateTime is the timestamp
Chain — event.get("start", {}).get("dateTime", "") is two safe hops
Row — [title, start] lands as two columns in the sheet

Layers of defense

Layer	Default
`event.get("start", {})`	empty dict
`.get("dateTime", "")`	empty string
row fallback	`["", ""]` — columns stay aligned

Day 26 · ~12 min●

Events carry more structure than emails — a title lives under one key, a start time lives in a nested dict. What's the clean way to pull both into one row?

Read summary off the event for the title, reach into start.dateTime for the timestamp, then pass both as one row to the append call?

Exactly. event.get("start", {}) first to grab the nested dict safely, then .get("dateTime", "") for the string. Two layers, two defaults, no crashes:

python

events = toolset.execute_action(Action.GOOGLECALENDAR_FIND_EVENT, {"query": query})
items = events.get("items", [])
for event in items:
    title = event.get("summary", "")
    start = event.get("start", {}).get("dateTime", "")

.get("start", {}).get("dateTime", "") chained — if start is missing, the {} default keeps the second .get safe?

Exactly. An empty dict still supports .get, so the second call returns "". Your row always has two strings in it regardless of what shape the event carries:

python

def calendar_to_sheet(query: str, spreadsheet_id: str) -> int:
    events = toolset.execute_action(Action.GOOGLECALENDAR_FIND_EVENT, {"query": query})
    items = events.get("items", [])
    count = 0
    for event in items:
        title = event.get("summary", "")
        start = event.get("start", {}).get("dateTime", "")
        toolset.execute_action(Action.GOOGLESHEETS_SPREADSHEETS_VALUES_APPEND, {
            "spreadsheetId": spreadsheet_id, "range": "Sheet1",
            "values": [[title, start]], "valueInputOption": "USER_ENTERED",
        })
        count += 1
    return count

What if an event has no summary — is an empty title useful or should I skip it?

So every matching event becomes a row — title column, timestamp column — ready for pivots or charts?

That is the payoff of a structured log. A pivot table on two clean columns beats a scroll through a calendar every time.

Nested .get() Chains

TL;DR: Reach into nested dicts with .get(key, {}) before the next .get — every layer defaults.

Events — summary is the title, start.dateTime is the timestamp
Chain — event.get("start", {}).get("dateTime", "") is two safe hops
Row — [title, start] lands as two columns in the sheet

Layers of defense

Layer	Default
`event.get("start", {})`	empty dict
`.get("dateTime", "")`	empty string
row fallback	`["", ""]` — columns stay aligned

events = toolset.execute_action(Action.GOOGLECALENDAR_FIND_EVENT, {"query": query}) items = events.get("items", []) for event in items: title = event.get("summary", "") start = event.get("start", {}).get("dateTime", "")

def calendar_to_sheet(query: str, spreadsheet_id: str) -> int: events = toolset.execute_action(Action.GOOGLECALENDAR_FIND_EVENT, {"query": query}) items = events.get("items", []) count = 0 for event in items: title = event.get("summary", "") start = event.get("start", {}).get("dateTime", "") toolset.execute_action(Action.GOOGLESHEETS_SPREADSHEETS_VALUES_APPEND, { "spreadsheetId": spreadsheet_id, "range": "Sheet1", "values": [[title, start]], "valueInputOption": "USER_ENTERED", }) count += 1 return count

Nested .get() Chains

TL;DR: Reach into nested dicts with .get(key, {}) before the next .get — every layer defaults.

Events — summary is the title, start.dateTime is the timestamp

Chain — event.get("start", {}).get("dateTime", "") is two safe hops

Row — [title, start] lands as two columns in the sheet

Layers of defense

Layer	Default
`event.get("start", {})`	empty dict
`.get("dateTime", "")`	empty string
row fallback	`["", ""]` — columns stay aligned

Nested .get() Chains

TL;DR: Reach into nested dicts with .get(key, {}) before the next .get — every layer defaults.

Events — summary is the title, start.dateTime is the timestamp

Chain — event.get("start", {}).get("dateTime", "") is two safe hops

Row — [title, start] lands as two columns in the sheet

Layers of defense

Layer	Default
`event.get("start", {})`	empty dict
`.get("dateTime", "")`	empty string
row fallback	`["", ""]` — columns stay aligned

Nested .get() Chains

Layers of defense

Nested .get() Chains

Layers of defense

Nested .get() Chains

Layers of defense

Sign up to practice

Nested .get() Chains

Layers of defense

Sign up to practice