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.

Send an Email: Delivering From Python — Automation For Beginners | zuzu.codes

Day 7 · ~12 min●

Yesterday's draft sits quietly in your Drafts folder. Today you send — the message actually leaves your outbox. What do you think changes in the params?

The API needs a recipient now. Subject and body aren't enough — it has to know who's getting the email.

Exactly. Action.GMAIL_SEND_EMAIL takes a recipient_email alongside subject and body. The response confirms the send with the new message's id and labels (SENT is usually there):

python

result = toolset.execute_action(Action.GMAIL_SEND_EMAIL, {
    "recipient_email": "me@example.com",
    "subject": "Test from Python",
    "body": "Hello.",
})

Sending to yourself is a nice trick — the message arrives in my own inbox so I can confirm it worked?

That's the safest way to verify a send action from code. You see the delivered message in your inbox within seconds. Wrap the call in a named function so any workflow can reuse it:

python

def send_email(recipient: str, subject: str, body: str) -> dict:
    result = toolset.execute_action(Action.GMAIL_SEND_EMAIL, {
        "recipient_email": recipient,
        "subject": subject,
        "body": body,
    })
    return result

Is this undoable? If my function sends to the wrong address, can I recall it?

No. Unlike drafts, a sent email leaves your server immediately. That is why write actions always deserve an extra check before they run — pair this function with a confirmation step in real workflows, or use the draft action first and only send when something approves it.

So after this, my Python can fully operate Gmail — count, read, search, draft, send. That covers every verb a human uses?

Every verb a human uses on the Gmail UI now has a Python twin in your head. Week 2 moves the same pattern to Calendar and Tasks.

Sending Mail From Code

TL;DR: GMAIL_SEND_EMAIL takes a recipient, subject, body — and the message leaves immediately.

Params — {"recipient_email": ..., "subject": ..., "body": ...}
Response — dict with id, threadId, labelIds (includes SENT)
Safety — send to yourself first; the inbox confirms delivery in seconds
No undo — once the server accepts the request, it leaves your account

Draft vs send

Action	Effect
`GMAIL_CREATE_EMAIL_DRAFT`	saves to Drafts, no delivery
`GMAIL_SEND_EMAIL`	delivers immediately, shows up in recipient inbox

Pair send actions with a review step when the recipient is anyone but you.

Sign up to practice

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

Day 7 · ~12 min●

Yesterday's draft sits quietly in your Drafts folder. Today you send — the message actually leaves your outbox. What do you think changes in the params?

The API needs a recipient now. Subject and body aren't enough — it has to know who's getting the email.

Exactly. Action.GMAIL_SEND_EMAIL takes a recipient_email alongside subject and body. The response confirms the send with the new message's id and labels (SENT is usually there):

python

result = toolset.execute_action(Action.GMAIL_SEND_EMAIL, {
    "recipient_email": "me@example.com",
    "subject": "Test from Python",
    "body": "Hello.",
})

Sending to yourself is a nice trick — the message arrives in my own inbox so I can confirm it worked?

That's the safest way to verify a send action from code. You see the delivered message in your inbox within seconds. Wrap the call in a named function so any workflow can reuse it:

python

def send_email(recipient: str, subject: str, body: str) -> dict:
    result = toolset.execute_action(Action.GMAIL_SEND_EMAIL, {
        "recipient_email": recipient,
        "subject": subject,
        "body": body,
    })
    return result

Is this undoable? If my function sends to the wrong address, can I recall it?

So after this, my Python can fully operate Gmail — count, read, search, draft, send. That covers every verb a human uses?

Every verb a human uses on the Gmail UI now has a Python twin in your head. Week 2 moves the same pattern to Calendar and Tasks.

Sending Mail From Code

TL;DR: GMAIL_SEND_EMAIL takes a recipient, subject, body — and the message leaves immediately.

Params — {"recipient_email": ..., "subject": ..., "body": ...}
Response — dict with id, threadId, labelIds (includes SENT)
Safety — send to yourself first; the inbox confirms delivery in seconds
No undo — once the server accepts the request, it leaves your account

Draft vs send

Action	Effect
`GMAIL_CREATE_EMAIL_DRAFT`	saves to Drafts, no delivery
`GMAIL_SEND_EMAIL`	delivers immediately, shows up in recipient inbox

Pair send actions with a review step when the recipient is anyone but you.