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.

Email to Task: Your First Cross-App Chain — Automation For Beginners

Day 24 · ~12 min●

First cross-app chain. Read the newest email, turn its snippet into a new Google Task. What's the shape of a two-API function?

Call Gmail to get the list, guard against empty, pull the first snippet, then call Tasks to insert it as a title?

Exactly. Two execute_action calls, one transformation between them. The Gmail call is just like Day 4; the Tasks call is just like Day 14:

python

emails = toolset.execute_action(Action.GMAIL_FETCH_EMAILS, {"max_results": max_results})
messages = emails.get("messages", [])
if not messages:
    return {}
snippet = messages[0].get("snippet", "No subject")

And then I hand that snippet straight to the Tasks insert call as the title?

Exactly. Slice the snippet down if it's long, then call the second API. Return the dict from the Tasks call so the caller sees the new task id and can open it in the UI:

python

def email_to_task(max_results: int) -> dict:
    emails = toolset.execute_action(Action.GMAIL_FETCH_EMAILS, {"max_results": max_results})
    messages = emails.get("messages", [])
    if not messages:
        return {}
    title = messages[0].get("snippet", "No subject")[:100]
    return toolset.execute_action(Action.GOOGLETASKS_INSERT_TASK, {
        "title": title, "tasklist_id": "@default", "status": "needsAction",
    })

Why slice to 100 characters? Do Tasks reject long titles?

Long titles render badly in the Tasks UI and can hit length limits. [:100] is a defensive cap — you keep the essence of the email without wrapping a full paragraph into a task title. Small detail, big UX win.

So one function bridges two apps — a real email on the left, a real task on the right, no human in between?

That is the whole point of chained automation. Your Python code moves information between apps faster than any copy-paste ever could.

Two APIs in One Function

TL;DR: Chain two execute_action calls with a transformation between them. Guard the first result before the second call runs.

Gmail step — fetch, guard empty list, pull first snippet
Transform — slice the title down to a reasonable length
Tasks step — insert with tasklist_id="@default" and return the dict

Why early returns matter in chains

Step	Risk
empty inbox	skip the Tasks call entirely
missing snippet	default `"No subject"` saves you

Day 24 · ~12 min●

First cross-app chain. Read the newest email, turn its snippet into a new Google Task. What's the shape of a two-API function?

Call Gmail to get the list, guard against empty, pull the first snippet, then call Tasks to insert it as a title?

Exactly. Two execute_action calls, one transformation between them. The Gmail call is just like Day 4; the Tasks call is just like Day 14:

python

emails = toolset.execute_action(Action.GMAIL_FETCH_EMAILS, {"max_results": max_results})
messages = emails.get("messages", [])
if not messages:
    return {}
snippet = messages[0].get("snippet", "No subject")

And then I hand that snippet straight to the Tasks insert call as the title?

Exactly. Slice the snippet down if it's long, then call the second API. Return the dict from the Tasks call so the caller sees the new task id and can open it in the UI:

python

def email_to_task(max_results: int) -> dict:
    emails = toolset.execute_action(Action.GMAIL_FETCH_EMAILS, {"max_results": max_results})
    messages = emails.get("messages", [])
    if not messages:
        return {}
    title = messages[0].get("snippet", "No subject")[:100]
    return toolset.execute_action(Action.GOOGLETASKS_INSERT_TASK, {
        "title": title, "tasklist_id": "@default", "status": "needsAction",
    })

Why slice to 100 characters? Do Tasks reject long titles?

So one function bridges two apps — a real email on the left, a real task on the right, no human in between?

That is the whole point of chained automation. Your Python code moves information between apps faster than any copy-paste ever could.

Two APIs in One Function

TL;DR: Chain two execute_action calls with a transformation between them. Guard the first result before the second call runs.

Gmail step — fetch, guard empty list, pull first snippet
Transform — slice the title down to a reasonable length
Tasks step — insert with tasklist_id="@default" and return the dict

Why early returns matter in chains

Step	Risk
empty inbox	skip the Tasks call entirely
missing snippet	default `"No subject"` saves you

emails = toolset.execute_action(Action.GMAIL_FETCH_EMAILS, {"max_results": max_results}) messages = emails.get("messages", []) if not messages: return {} snippet = messages[0].get("snippet", "No subject")

def email_to_task(max_results: int) -> dict: emails = toolset.execute_action(Action.GMAIL_FETCH_EMAILS, {"max_results": max_results}) messages = emails.get("messages", []) if not messages: return {} title = messages[0].get("snippet", "No subject")[:100] return toolset.execute_action(Action.GOOGLETASKS_INSERT_TASK, { "title": title, "tasklist_id": "@default", "status": "needsAction", })

Two APIs in One Function

TL;DR: Chain two execute_action calls with a transformation between them. Guard the first result before the second call runs.

Gmail step — fetch, guard empty list, pull first snippet

Transform — slice the title down to a reasonable length

Tasks step — insert with tasklist_id="@default" and return the dict

Why early returns matter in chains

Step	Risk
empty inbox	skip the Tasks call entirely
missing snippet	default `"No subject"` saves you

Two APIs in One Function

TL;DR: Chain two execute_action calls with a transformation between them. Guard the first result before the second call runs.

Gmail step — fetch, guard empty list, pull first snippet

Transform — slice the title down to a reasonable length

Tasks step — insert with tasklist_id="@default" and return the dict

Why early returns matter in chains

Step	Risk
empty inbox	skip the Tasks call entirely
missing snippet	default `"No subject"` saves you

Two APIs in One Function

Why early returns matter in chains

Two APIs in One Function

Why early returns matter in chains

Two APIs in One Function

Why early returns matter in chains

Sign up to practice

Two APIs in One Function

Why early returns matter in chains

Sign up to practice