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 Email Subject and Sender by Message ID — Automation For Freelancers

Day 4 · ~12 min●

count_emails from yesterday tells you how many threads exist. But to build an invoice-aware filter, you need the subjects and senders. How do you get the details of a specific message?

A different action. The count call gave me IDs. Now I pass an ID to get the full message.

Exactly the list-then-fetch pattern. GMAIL_FETCH_EMAILS returns lightweight summaries with IDs. GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID takes one ID and returns the full message dict — subject, from, body, date:

python

msg_id = "abc123"
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 separate actions instead of just returning the full message in the first fetch?

Efficiency. GMAIL_FETCH_EMAILS returns lightweight objects — IDs and snippets — for scanning many messages at once without downloading bodies. You scan the list to find what matters, then fetch only those messages in full. This pattern repeats across Calendar, Tasks, and Sheets later.

So I can count first, then filter the IDs for invoice subjects, then fetch only those full messages.

Three lines, three calls, your entire invoice-monitoring workflow:

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 can now read any email in my inbox from code. My invoice thread monitoring is two function calls away.

One caution: the response shape varies by email. Always use .get() with a default for every field — subject, from, body — because Gmail may omit fields on certain message types.

Reading a Specific Email by ID

GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID takes a single message ID and returns the full message dict, including subject, from, and body fields:

python

result = toolset.execute_action(
    action=Action.GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID,
    params={'messageId': msg_id}
)

The message dict

The response dict typically includes: messageId, subject, from, date, body (plain text), and snippet. Always check the shape of what comes back before accessing keys — field names can vary across email clients and encoding formats.

Read before you write — this lesson is a pure read operation. No emails are modified or sent.

Day 4 · ~12 min●

count_emails from yesterday tells you how many threads exist. But to build an invoice-aware filter, you need the subjects and senders. How do you get the details of a specific message?

A different action. The count call gave me IDs. Now I pass an ID to get the full message.

python

msg_id = "abc123"
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 separate actions instead of just returning the full message in the first fetch?

So I can count first, then filter the IDs for invoice subjects, then fetch only those full messages.

Three lines, three calls, your entire invoice-monitoring workflow:

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 can now read any email in my inbox from code. My invoice thread monitoring is two function calls away.

One caution: the response shape varies by email. Always use .get() with a default for every field — subject, from, body — because Gmail may omit fields on certain message types.

Reading a Specific Email by ID

GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID takes a single message ID and returns the full message dict, including subject, from, and body fields:

python

result = toolset.execute_action(
    action=Action.GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID,
    params={'messageId': msg_id}
)

The message dict

Read before you write — this lesson is a pure read operation. No emails are modified or sent.

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

Reading a Specific Email by ID

GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID takes a single message ID and returns the full message dict, including subject, from, and body fields:

python

result = toolset.execute_action(
    action=Action.GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID,
    params={'messageId': msg_id}
)

The message dict

Read before you write — this lesson is a pure read operation. No emails are modified or sent.

Reading a Specific Email by ID

GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID takes a single message ID and returns the full message dict, including subject, from, and body fields:

python

result = toolset.execute_action(
    action=Action.GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID,
    params={'messageId': msg_id}
)

The message dict

Read before you write — this lesson is a pure read operation. No emails are modified or sent.

Reading a Specific Email by ID

The message dict

Reading a Specific Email by ID

The message dict

Reading a Specific Email by ID

The message dict

Sign up to practice

Reading a Specific Email by ID

The message dict

Sign up to practice