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 an Investor Update Email with Composio — Automation For Entrepreneurs

Day 6 · ~12 min●

You can search your inbox with search_emails. Now the other side: putting an email into Gmail. What's the last thing you drafted manually?

After search_emails I can find investor threads. The other half is drafting the weekly update — subject, body, formatted metrics. I still do that by hand every Monday.

GMAIL_CREATE_EMAIL_DRAFT saves a draft to your Gmail without sending it. You get to review it before it goes anywhere. The pattern is always draft-first, send-second for any write action:

python

result = toolset.execute_action(
    Action.GMAIL_CREATE_EMAIL_DRAFT,
    {"to": to, "subject": subject, "body": body}
)
print(result.get("id", "no draft id"))

Why draft instead of send directly? The body is already formatted — what's the point of the extra step?

Safety. A draft gives you one last look — wrong recipient, typo in MRR, missing metric. GMAIL_SEND_EMAIL is irreversible. Drafts are free to discard. In any automated workflow, always draft, review, then send. Here's the full function:

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', 'no id')}")
    return result

So I can chain investor_update(metrics) from the Python track into draft_email — formatted update goes straight into Gmail drafts, ready to review.

Your Monday morning just became: run investor_update, pass the output to draft_email, open Gmail to review. Two function calls and one click to send.

The Python track built the formatter. The automation track connects it to the real app. They compose perfectly.

Always log the draft ID returned by the action. If something goes wrong downstream, the draft ID lets you retrieve and debug. result.get('id') is your audit trail.

Creating an Email Draft

GMAIL_CREATE_EMAIL_DRAFT saves to Gmail Drafts without sending.

python

toolset.execute_action(
    Action.GMAIL_CREATE_EMAIL_DRAFT,
    {"to": "me@example.com", "subject": "...", "body": "..."}
)

Safety rule for write actions

Always draft first in automated workflows:

draft_email(to, subject, body) — saves draft, no delivery
Inspect the draft in Gmail UI
send_email(to, subject, body) — only when confident

Pitfall

Don't skip the draft step in production workflows. Automated sends with a wrong recipient are very hard to undo.

Day 6 · ~12 min●

You can search your inbox with search_emails. Now the other side: putting an email into Gmail. What's the last thing you drafted manually?

After search_emails I can find investor threads. The other half is drafting the weekly update — subject, body, formatted metrics. I still do that by hand every Monday.

GMAIL_CREATE_EMAIL_DRAFT saves a draft to your Gmail without sending it. You get to review it before it goes anywhere. The pattern is always draft-first, send-second for any write action:

python

result = toolset.execute_action(
    Action.GMAIL_CREATE_EMAIL_DRAFT,
    {"to": to, "subject": subject, "body": body}
)
print(result.get("id", "no draft id"))

Why draft instead of send directly? The body is already formatted — what's the point of the extra step?

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', 'no id')}")
    return result

So I can chain investor_update(metrics) from the Python track into draft_email — formatted update goes straight into Gmail drafts, ready to review.

Your Monday morning just became: run investor_update, pass the output to draft_email, open Gmail to review. Two function calls and one click to send.

The Python track built the formatter. The automation track connects it to the real app. They compose perfectly.

Always log the draft ID returned by the action. If something goes wrong downstream, the draft ID lets you retrieve and debug. result.get('id') is your audit trail.

Creating an Email Draft

GMAIL_CREATE_EMAIL_DRAFT saves to Gmail Drafts without sending.

python

toolset.execute_action(
    Action.GMAIL_CREATE_EMAIL_DRAFT,
    {"to": "me@example.com", "subject": "...", "body": "..."}
)

Safety rule for write actions

Always draft first in automated workflows:

draft_email(to, subject, body) — saves draft, no delivery
Inspect the draft in Gmail UI
send_email(to, subject, body) — only when confident

Pitfall

Don't skip the draft step in production workflows. Automated sends with a wrong recipient are very hard to undo.

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', 'no id')}") return result

Creating an Email Draft

GMAIL_CREATE_EMAIL_DRAFT saves to Gmail Drafts without sending.

python

toolset.execute_action(
    Action.GMAIL_CREATE_EMAIL_DRAFT,
    {"to": "me@example.com", "subject": "...", "body": "..."}
)

Safety rule for write actions

Always draft first in automated workflows:

draft_email(to, subject, body) — saves draft, no delivery

Inspect the draft in Gmail UI

send_email(to, subject, body) — only when confident

Pitfall

Don't skip the draft step in production workflows. Automated sends with a wrong recipient are very hard to undo.

Creating an Email Draft

GMAIL_CREATE_EMAIL_DRAFT saves to Gmail Drafts without sending.

python

toolset.execute_action(
    Action.GMAIL_CREATE_EMAIL_DRAFT,
    {"to": "me@example.com", "subject": "...", "body": "..."}
)

Safety rule for write actions

Always draft first in automated workflows:

draft_email(to, subject, body) — saves draft, no delivery

Inspect the draft in Gmail UI

send_email(to, subject, body) — only when confident

Pitfall

Don't skip the draft step in production workflows. Automated sends with a wrong recipient are very hard to undo.

Creating an Email Draft

Safety rule for write actions

Pitfall

Creating an Email Draft

Safety rule for write actions

Pitfall

Creating an Email Draft

Safety rule for write actions

Pitfall

Sign up to practice

Creating an Email Draft

Safety rule for write actions

Pitfall

Sign up to practice