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.

Privacy Terms

Day 16 · ~11 min●

First chain. Read 1 email's subject. Create a Calendar event whose title is that subject. Two execute_action calls, one transformation between them.

python

result = toolset.execute_action(Action.GMAIL_FETCH_EMAILS, {"max_results": 1})
messages = result.get("messages", [])
first_subject = messages[0].get("subject", "(no subject)") if messages else "(empty inbox)"

event = toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {
    "calendar_id": "primary",
    "summary": f"Latest inbox: {first_subject}",
    "start_datetime": "2026-12-31T08:00:00+00:00",
    "event_duration_minutes": 15,
})

No new APIs — just two from prior lessons stitched together?

That's the whole point of week 3. Composition. The hard part isn't any individual call; it's the plumbing — guard against empty results, transform shapes, handle the case where the read fails before the write fires.

What if the inbox is empty — should I still write?

Depends on the use case. The scaffold above writes "(empty inbox)" as the event title — sometimes that's the signal you want. Other times you'd if not messages: return and skip the write. Both are valid; pick what your workflow needs.

Read → Write — the basic chain

The shape:

Call API A, get a value back.
Transform / pick / filter the value in Python.
Pass the transformed value to API B.

python

# 1. read
result = toolset.execute_action(Action.GMAIL_FETCH_EMAILS, {"max_results": 1})
messages = result.get("messages", [])

# 2. transform
first_subject = messages[0].get("subject", "(no subject)") if messages else None

# 3. write
if first_subject:
    toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {
        "calendar_id": "primary",
        "summary": f"Latest inbox: {first_subject}",
        "start_datetime": "2026-12-31T08:00:00+00:00",
        "event_duration_minutes": 15,
    })

Defensive transformation

The transformation step is where most chain bugs live. The read could return:

empty messages list (inbox empty)
messages not in the dict at all (API edge case)
a message without a subject field (some emails)

.get(key, default) handles each layer. Without it, the script crashes mid-chain — and the write never fires, so users notice.

Conditional write

If you genuinely don't want to write on empty:

python

if not messages:
    print("empty inbox — nothing to forward")
    return    # or `import sys; sys.exit(0)`

Clear signal vs. writing an empty-shaped record you'll then have to filter on the consumer side.

Avoid silent failures

A chain that partially succeeds is worse than one that fully fails. If the read works but the write fails, you'd want to know. Catch and log:

python

try:
    toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {...})
except Exception as e:
    print(f"Calendar create failed: {type(e).__name__}: {e}")

Day 19 of this track formalizes the "log every step" pattern.

Sign up to practice

Create a free account to get started. Paid plans unlock all tracks.

or

Day 16 · ~11 min●

First chain. Read 1 email's subject. Create a Calendar event whose title is that subject. Two execute_action calls, one transformation between them.

python

result = toolset.execute_action(Action.GMAIL_FETCH_EMAILS, {"max_results": 1})
messages = result.get("messages", [])
first_subject = messages[0].get("subject", "(no subject)") if messages else "(empty inbox)"

event = toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {
    "calendar_id": "primary",
    "summary": f"Latest inbox: {first_subject}",
    "start_datetime": "2026-12-31T08:00:00+00:00",
    "event_duration_minutes": 15,
})

No new APIs — just two from prior lessons stitched together?

That's the whole point of week 3. Composition. The hard part isn't any individual call; it's the plumbing — guard against empty results, transform shapes, handle the case where the read fails before the write fires.

What if the inbox is empty — should I still write?

Depends on the use case. The scaffold above writes "(empty inbox)" as the event title — sometimes that's the signal you want. Other times you'd if not messages: return and skip the write. Both are valid; pick what your workflow needs.

Read → Write — the basic chain

The shape:

Call API A, get a value back.
Transform / pick / filter the value in Python.
Pass the transformed value to API B.

python

# 1. read
result = toolset.execute_action(Action.GMAIL_FETCH_EMAILS, {"max_results": 1})
messages = result.get("messages", [])

# 2. transform
first_subject = messages[0].get("subject", "(no subject)") if messages else None

# 3. write
if first_subject:
    toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {
        "calendar_id": "primary",
        "summary": f"Latest inbox: {first_subject}",
        "start_datetime": "2026-12-31T08:00:00+00:00",
        "event_duration_minutes": 15,
    })

Defensive transformation

The transformation step is where most chain bugs live. The read could return:

empty messages list (inbox empty)
messages not in the dict at all (API edge case)
a message without a subject field (some emails)

.get(key, default) handles each layer. Without it, the script crashes mid-chain — and the write never fires, so users notice.

Conditional write

If you genuinely don't want to write on empty:

python

if not messages:
    print("empty inbox — nothing to forward")
    return    # or `import sys; sys.exit(0)`

Clear signal vs. writing an empty-shaped record you'll then have to filter on the consumer side.

Avoid silent failures

A chain that partially succeeds is worse than one that fully fails. If the read works but the write fails, you'd want to know. Catch and log:

python

try:
    toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {...})
except Exception as e:
    print(f"Calendar create failed: {type(e).__name__}: {e}")

Day 19 of this track formalizes the "log every step" pattern.

Sign up to practice

Create a free account to get started. Paid plans unlock all tracks.

or