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.

Create a Calendar Event from Python — Automation For Entrepreneurs | zuzu.codes

Day 12 · ~12 min●

Your find_events shows upcoming meetings. Now the other side — creating one. What's the last event you booked manually that could have been automated?

After find_events I can see what's already scheduled. But every time a customer books a demo through our website, I manually create the calendar event and add my co-founder. That's 3 minutes per booking, maybe 10 bookings a week.

GOOGLECALENDAR_CREATE_EVENT creates the event for you. You need the calendar ID, title, and ISO8601 start and end datetimes. The event appears in Google Calendar exactly as if you'd booked it manually:

python

result = toolset.execute_action(
    Action.GOOGLECALENDAR_CREATE_EVENT,
    {"calendar_id": cal_id, "summary": title, "start": {"dateTime": start}, "end": {"dateTime": end}}
)
print(result.get("id", "no event id"))

Does start take a string or an object? The nested {"dateTime": start} shape is different from what I've seen before.

The Calendar API wraps datetimes in an object: {"dateTime": "2026-04-22T09:00:00Z"}. Some events also include a "timeZone" field. Keep a note about timezone: always confirm the time zone in your workflow — a UTC start time renders in your local calendar's timezone. Here's the full function:

python

def create_event(cal_id: str, title: str, start: str, end: str) -> dict:
    result = toolset.execute_action(
        Action.GOOGLECALENDAR_CREATE_EVENT,
        {"calendar_id": cal_id, "summary": title, "start": {"dateTime": start}, "end": {"dateTime": end}}
    )
    print(f"Created event: {result.get('id', 'no id')}")
    return result

So every demo booking webhook can call create_event automatically. 30 seconds instead of 3 minutes, 10 times a week. That's 25 minutes back.

25 minutes a week is 21 hours a year. That's a real ops hire you're not making.

Find-then-create is the pattern. Check the calendar first with find_events, then create the event. No duplicates.

Always confirm the time zone — add "timeZone": "America/New_York" or your local zone inside the start and end objects. UTC works, but a board member in a different timezone will see a confusing time if you rely on calendar display conversion.

Creating a Calendar Event

GOOGLECALENDAR_CREATE_EVENT creates an event on your calendar. Automating demo booking events eliminates 3 minutes of manual entry per booking — at 10 bookings a week that's 25 minutes reclaimed every week.

python

toolset.execute_action(
    Action.GOOGLECALENDAR_CREATE_EVENT,
    {
      "calendar_id": "primary",
      "summary": "Board Meeting",
      "start": {"dateTime": "2026-04-22T09:00:00Z"},
      "end": {"dateTime": "2026-04-22T10:00:00Z"}
    }
)

Pitfall

Always confirm the time zone. UTC datetimes display in the viewer's local timezone — add "timeZone": "America/New_York" inside the start/end objects to be explicit.

Sign up to practice

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

Day 12 · ~12 min●

Your find_events shows upcoming meetings. Now the other side — creating one. What's the last event you booked manually that could have been automated?

python

result = toolset.execute_action(
    Action.GOOGLECALENDAR_CREATE_EVENT,
    {"calendar_id": cal_id, "summary": title, "start": {"dateTime": start}, "end": {"dateTime": end}}
)
print(result.get("id", "no event id"))

Does start take a string or an object? The nested {"dateTime": start} shape is different from what I've seen before.

python

def create_event(cal_id: str, title: str, start: str, end: str) -> dict:
    result = toolset.execute_action(
        Action.GOOGLECALENDAR_CREATE_EVENT,
        {"calendar_id": cal_id, "summary": title, "start": {"dateTime": start}, "end": {"dateTime": end}}
    )
    print(f"Created event: {result.get('id', 'no id')}")
    return result

So every demo booking webhook can call create_event automatically. 30 seconds instead of 3 minutes, 10 times a week. That's 25 minutes back.

25 minutes a week is 21 hours a year. That's a real ops hire you're not making.

Find-then-create is the pattern. Check the calendar first with find_events, then create the event. No duplicates.

Creating a Calendar Event

python

toolset.execute_action(
    Action.GOOGLECALENDAR_CREATE_EVENT,
    {
      "calendar_id": "primary",
      "summary": "Board Meeting",
      "start": {"dateTime": "2026-04-22T09:00:00Z"},
      "end": {"dateTime": "2026-04-22T10:00:00Z"}
    }
)

Pitfall

Always confirm the time zone. UTC datetimes display in the viewer's local timezone — add "timeZone": "America/New_York" inside the start/end objects to be explicit.