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.

Draft a Co-Author Email Without Sending It — Automation For Researchers

Day 6 · ~12 min●

You need to send your research group a "revision round 3" status update with the updated deadline. Before you automate that send, what should happen first?

search_emails from Day 5 showed me how to read — but sending feels different. A misformatted email to my journal editor would be embarrassing at minimum. I'd want to review it first.

That instinct is the right one. GMAIL_CREATE_EMAIL_DRAFT saves the email to your Drafts folder without delivering it. You can open Gmail, review the wording, edit the recipient if needed, then send manually — or automate the send on Day 7 after you've confirmed the draft looks right.

How do I see the draft I created? Does it appear immediately in Gmail?

Yes — open Gmail, click Drafts. It's there. Any draft created by GMAIL_CREATE_EMAIL_DRAFT is a real draft in your account. You can edit it in the browser, forward it, or delete it. The response dict includes the draft ID so you can reference it later:

python

def draft_email(to: str, subject: str, body: str) -> dict:
    result = toolset.execute_action(
        Action.GMAIL_CREATE_EMAIL_DRAFT,
        {"to": to, "subject": subject, "body": body}
    )
    print(f"Draft created: {result.get('id', 'unknown')}")
    return result

So I can automate the draft composition — subject line with the revision round number, body with the updated deadline — and just review it in Gmail before sending. The boring parts are automated, the judgment call stays with me.

The revision cover letter, generated in seconds. Your job is verifying that "Dr. Smith" is spelled correctly.

I've drafted that email manually eight times this year. Now it's one function call away from being pre-populated with the right fields.

The test-first pattern applies to every write action:

python

# Test with yourself first
result = draft_email("myemail@uni.ac.uk", "Test", "Draft content")
print(result)

One mis-sent email to a journal editor is a career memory. The draft step is your confirmation checkpoint.

Drafts vs Sends

GMAIL_CREATE_EMAIL_DRAFT is a safe write action — it creates the email in your Drafts folder with no delivery.

GMAIL_SEND_EMAIL is irreversible — the message is delivered immediately. No undo.

When to draft

Any email where recipient or wording needs review before sending
Templates you want to customise per recipient
Batch operations where you want to inspect one before automating the rest

Response shape

python

{"id": "draft_xyz", "message": {...}}

The id is the draft's Gmail ID. Keep it if you want to send the draft programmatically later.

Day 6 · ~12 min●

You need to send your research group a "revision round 3" status update with the updated deadline. Before you automate that send, what should happen first?

search_emails from Day 5 showed me how to read — but sending feels different. A misformatted email to my journal editor would be embarrassing at minimum. I'd want to review it first.

How do I see the draft I created? Does it appear immediately in Gmail?

python

def draft_email(to: str, subject: str, body: str) -> dict:
    result = toolset.execute_action(
        Action.GMAIL_CREATE_EMAIL_DRAFT,
        {"to": to, "subject": subject, "body": body}
    )
    print(f"Draft created: {result.get('id', 'unknown')}")
    return result

The revision cover letter, generated in seconds. Your job is verifying that "Dr. Smith" is spelled correctly.

I've drafted that email manually eight times this year. Now it's one function call away from being pre-populated with the right fields.

The test-first pattern applies to every write action:

python

# Test with yourself first
result = draft_email("myemail@uni.ac.uk", "Test", "Draft content")
print(result)

One mis-sent email to a journal editor is a career memory. The draft step is your confirmation checkpoint.

Drafts vs Sends

GMAIL_CREATE_EMAIL_DRAFT is a safe write action — it creates the email in your Drafts folder with no delivery.

GMAIL_SEND_EMAIL is irreversible — the message is delivered immediately. No undo.

When to draft

Any email where recipient or wording needs review before sending
Templates you want to customise per recipient
Batch operations where you want to inspect one before automating the rest

Response shape

python

{"id": "draft_xyz", "message": {...}}

The id is the draft's Gmail ID. Keep it if you want to send the draft programmatically later.

def draft_email(to: str, subject: str, body: str) -> dict: result = toolset.execute_action( Action.GMAIL_CREATE_EMAIL_DRAFT, {"to": to, "subject": subject, "body": body} ) print(f"Draft created: {result.get('id', 'unknown')}") return result

Drafts vs Sends

GMAIL_CREATE_EMAIL_DRAFT is a safe write action — it creates the email in your Drafts folder with no delivery.

GMAIL_SEND_EMAIL is irreversible — the message is delivered immediately. No undo.

When to draft

Any email where recipient or wording needs review before sending

Templates you want to customise per recipient

Batch operations where you want to inspect one before automating the rest

Response shape

python

{"id": "draft_xyz", "message": {...}}

The id is the draft's Gmail ID. Keep it if you want to send the draft programmatically later.

Drafts vs Sends

GMAIL_CREATE_EMAIL_DRAFT is a safe write action — it creates the email in your Drafts folder with no delivery.

GMAIL_SEND_EMAIL is irreversible — the message is delivered immediately. No undo.

When to draft

Any email where recipient or wording needs review before sending

Templates you want to customise per recipient

Batch operations where you want to inspect one before automating the rest

Response shape

python

{"id": "draft_xyz", "message": {...}}

The id is the draft's Gmail ID. Keep it if you want to send the draft programmatically later.

Drafts vs Sends

When to draft

Response shape

Drafts vs Sends

When to draft

Response shape

Drafts vs Sends

When to draft

Response shape

Sign up to practice

Drafts vs Sends

When to draft

Response shape

Sign up to practice