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.

Fetch a Co-Author Email by Message ID — Automation For Researchers

Day 4 · ~12 min●

count_emails from Day 3 gives you a list of message dicts — each one has an id field. Your co-author sent a reply with the subject "Manuscript revision — round 3". How do you read the full message?

count_emails returns the count from the messages list — each message has an id. I'd take one of those IDs and pass it to a fetch action to get the full content.

Exactly the list-then-fetch pattern. GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID takes one message ID and returns the full email — subject, sender, body snippet. The response is a dict you parse the same way:

python

result = toolset.execute_action(
    Action.GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID,
    {"message_id": msg_id}
)
subject = result.get("subject", "")
sender = result.get("from", "")

Why two actions? Why doesn't GMAIL_FETCH_EMAILS just return the full body directly?

API efficiency. Fetching full bodies for 40 messages at once transfers a lot of data. GMAIL_FETCH_EMAILS returns lightweight summaries — IDs and snippets — so you scan quickly. You only fetch full content for the messages that matter. Same pattern as filter_eligible in the Python track: filter first, fetch detail for what passes.

So the workflow is: count_emails to get IDs, then get_email on the ones with "revision" in the subject. That's the inbox triage I described on Day 3.

Triage without opening a browser. That's what automation feels like:

python

def get_email(msg_id: str) -> dict:
    result = toolset.execute_action(
        Action.GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID,
        {"message_id": msg_id}
    )
    print(f"Fetched: {result.get('subject', 'no subject')}")
    return result

I'm reading my actual co-author emails from a Python function. That's a genuinely new research tool.

One thing to note: GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID fetches a single message at a time. For bulk operations — like archiving all "sounds good" replies — loop over the IDs from count_emails and call get_email for each. Tests use a real message ID from your inbox, so the first test run is worth doing interactively.

The List-Then-Fetch Pattern

This pattern appears in every REST API in this track:

List — fetch lightweight summaries with IDs (GMAIL_FETCH_EMAILS)
Fetch — retrieve full details for the IDs you care about (GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID)

python

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

# Step 2: fetch full details for the first message
if messages:
    full = toolset.execute_action(
        Action.GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID,
        {"message_id": messages[0]["id"]}
    )

Response keys

The full message dict typically includes subject, from, to, snippet, body. Use .get(key, "") for all of them — the shape can vary.

Day 4 · ~12 min●

count_emails returns the count from the messages list — each message has an id. I'd take one of those IDs and pass it to a fetch action to get the full content.

python

result = toolset.execute_action(
    Action.GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID,
    {"message_id": msg_id}
)
subject = result.get("subject", "")
sender = result.get("from", "")

Why two actions? Why doesn't GMAIL_FETCH_EMAILS just return the full body directly?

So the workflow is: count_emails to get IDs, then get_email on the ones with "revision" in the subject. That's the inbox triage I described on Day 3.

Triage without opening a browser. That's what automation feels like:

python

def get_email(msg_id: str) -> dict:
    result = toolset.execute_action(
        Action.GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID,
        {"message_id": msg_id}
    )
    print(f"Fetched: {result.get('subject', 'no subject')}")
    return result

I'm reading my actual co-author emails from a Python function. That's a genuinely new research tool.

The List-Then-Fetch Pattern

This pattern appears in every REST API in this track:

List — fetch lightweight summaries with IDs (GMAIL_FETCH_EMAILS)
Fetch — retrieve full details for the IDs you care about (GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID)

python

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

# Step 2: fetch full details for the first message
if messages:
    full = toolset.execute_action(
        Action.GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID,
        {"message_id": messages[0]["id"]}
    )

Response keys

The full message dict typically includes subject, from, to, snippet, body. Use .get(key, "") for all of them — the shape can vary.

def get_email(msg_id: str) -> dict: result = toolset.execute_action( Action.GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID, {"message_id": msg_id} ) print(f"Fetched: {result.get('subject', 'no subject')}") return result

The List-Then-Fetch Pattern

This pattern appears in every REST API in this track:

List — fetch lightweight summaries with IDs (GMAIL_FETCH_EMAILS)

Fetch — retrieve full details for the IDs you care about (GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID)

python

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

# Step 2: fetch full details for the first message
if messages:
    full = toolset.execute_action(
        Action.GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID,
        {"message_id": messages[0]["id"]}
    )

Response keys

The full message dict typically includes subject, from, to, snippet, body. Use .get(key, "") for all of them — the shape can vary.

The List-Then-Fetch Pattern

This pattern appears in every REST API in this track:

List — fetch lightweight summaries with IDs (GMAIL_FETCH_EMAILS)

Fetch — retrieve full details for the IDs you care about (GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID)

python

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

# Step 2: fetch full details for the first message
if messages:
    full = toolset.execute_action(
        Action.GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID,
        {"message_id": messages[0]["id"]}
    )

Response keys

The full message dict typically includes subject, from, to, snippet, body. Use .get(key, "") for all of them — the shape can vary.

The List-Then-Fetch Pattern

Response keys

The List-Then-Fetch Pattern

Response keys

The List-Then-Fetch Pattern

Response keys

Sign up to practice

The List-Then-Fetch Pattern

Response keys

Sign up to practice