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 10 · ~12 min●

send_email from last week completed the Gmail loop. Calendar is the next app. Before creating events, you need to know which calendar to use. How many Google calendars do you actually have?

My personal one, my university research calendar, and a shared one for the lab group. Three calendars — and the IDs are somewhere in the Calendar settings, but I've never needed to look them up before.

toolset.execute_action follows the same pattern — GOOGLECALENDAR_LIST_CALENDARS returns a dict with a calendars key holding a list. Each calendar has an id and a summary (display name). Same .get() reflex you used for Gmail:

python

result = toolset.execute_action(Action.GOOGLECALENDAR_LIST_CALENDARS, {})
calendars = result.get("calendars", [])
for cal in calendars:
    print(f"{cal.get('summary')}: {cal.get('id')}")

GOOGLECALENDAR_LIST_CALENDARS — different namespace than Gmail, but the same toolset.execute_action wrapper? That's all that changes?

That's the pattern. The Action enum and the params dict are the only things that change between apps. The wrapper is always toolset.execute_action(Action.X, {...}). Learn the pattern once, use it everywhere:

python

def list_calendars() -> list:
    result = toolset.execute_action(Action.GOOGLECALENDAR_LIST_CALENDARS, {})
    calendars = result.get("calendars", [])
    print(f"Found {len(calendars)} calendars")
    return calendars

Three calendars back — personal, research, lab group. The research calendar ID is the one I need for the deadline events.

You'll never dig through Calendar settings for an ID again. One function call.

I'm applying the same .get() reflex I learned for Gmail to Calendar — the shape of the response is just slightly different.

Calendar IDs look like email addresses (primary, user@gmail.com, or a long hash). When you call GOOGLECALENDAR_FIND_EVENT or GOOGLECALENDAR_CREATE_EVENT, always retrieve the ID programmatically with list_calendars — never hardcode it. Calendar IDs can change if the calendar is deleted and recreated.

The Composio App Pattern

Every Composio app follows the same shape:

python

result = toolset.execute_action(Action.APP_ACTION_NAME, {params})
items = result.get("key", [])

Google Calendar response

GOOGLECALENDAR_LIST_CALENDARS returns {"calendars": [{"id": "...", "summary": "..."}, ...]}.

IDs in Calendar

Calendar	ID format
Primary	`"primary"` or email
Shared	Long hash string

Always look up IDs at runtime — never hardcode them. Calendar IDs change when accounts are migrated or calendars are deleted and recreated.

Sign up to practice

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

or

Day 10 · ~12 min●

send_email from last week completed the Gmail loop. Calendar is the next app. Before creating events, you need to know which calendar to use. How many Google calendars do you actually have?

My personal one, my university research calendar, and a shared one for the lab group. Three calendars — and the IDs are somewhere in the Calendar settings, but I've never needed to look them up before.

toolset.execute_action follows the same pattern — GOOGLECALENDAR_LIST_CALENDARS returns a dict with a calendars key holding a list. Each calendar has an id and a summary (display name). Same .get() reflex you used for Gmail:

python

result = toolset.execute_action(Action.GOOGLECALENDAR_LIST_CALENDARS, {})
calendars = result.get("calendars", [])
for cal in calendars:
    print(f"{cal.get('summary')}: {cal.get('id')}")

GOOGLECALENDAR_LIST_CALENDARS — different namespace than Gmail, but the same toolset.execute_action wrapper? That's all that changes?

That's the pattern. The Action enum and the params dict are the only things that change between apps. The wrapper is always toolset.execute_action(Action.X, {...}). Learn the pattern once, use it everywhere:

python

def list_calendars() -> list:
    result = toolset.execute_action(Action.GOOGLECALENDAR_LIST_CALENDARS, {})
    calendars = result.get("calendars", [])
    print(f"Found {len(calendars)} calendars")
    return calendars

Three calendars back — personal, research, lab group. The research calendar ID is the one I need for the deadline events.

You'll never dig through Calendar settings for an ID again. One function call.

I'm applying the same .get() reflex I learned for Gmail to Calendar — the shape of the response is just slightly different.

Calendar IDs look like email addresses (primary, user@gmail.com, or a long hash). When you call GOOGLECALENDAR_FIND_EVENT or GOOGLECALENDAR_CREATE_EVENT, always retrieve the ID programmatically with list_calendars — never hardcode it. Calendar IDs can change if the calendar is deleted and recreated.

The Composio App Pattern

Every Composio app follows the same shape:

python

result = toolset.execute_action(Action.APP_ACTION_NAME, {params})
items = result.get("key", [])

Google Calendar response

GOOGLECALENDAR_LIST_CALENDARS returns {"calendars": [{"id": "...", "summary": "..."}, ...]}.

IDs in Calendar

Calendar	ID format
Primary	`"primary"` or email
Shared	Long hash string

Always look up IDs at runtime — never hardcode them. Calendar IDs change when accounts are migrated or calendars are deleted and recreated.

Sign up to practice

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

or