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.

When tool calls fail — Automation Foundations

Day 7 · ~11 min●

API calls can fail. Network drop, bad argument, expired auth token. Without a try/except, a failed call crashes your script.

python

try:
    result = toolset.execute_action(Action.GMAIL_FETCH_EMAILS, {"max_results": -1})
    print("ok")
except Exception as e:
    print(type(e).__name__)

Exception catches anything?

Pretty much. Exception is the parent of most error types you'll meet. as e binds the error to a name so you can inspect it. type(e).__name__ is the class name of the error — RuntimeError, TypeError, etc. Useful for logging without dumping a full traceback.

What kinds of errors does Composio throw?

Mostly RuntimeError for tool-level failures (with a message describing what went wrong), and the special string AUTH_REQUIRED:<app> when the OAuth token has expired. The platform catches AUTH_REQUIRED and pops a re-connect dialog before your script's except can see it — so in practice you write try/except for transient errors, not auth.

`try/except` for tool calls

Network code is the natural home of try/except. Wrap every API call you can't guarantee will succeed:

python

try:
    result = toolset.execute_action(Action.GMAIL_FETCH_EMAILS, {"max_results": 5})
    messages = result.get("messages", [])
except Exception as e:
    print(f"Gmail fetch failed: {type(e).__name__}: {e}")
    messages = []    # graceful fallback

Catch broad to start, narrow as you learn

except Exception catches almost anything. As you get more specific, you might write:

python

except RuntimeError as e:
    # Composio's preferred error type
    ...
except ValueError as e:
    # bad argument shape
    ...

For a week-1 lesson, broad is fine. The platform's AUTH_REQUIRED flow is handled at a higher layer — your code won't see auth errors normally.

What `type(e).name` gives you

python

try:
    int("not a number")
except Exception as e:
    print(type(e).__name__)    # ValueError

Clean, single-word identification of the error class. Better for logs and quick diagnostics than the full message, which might include long stack traces.

What this lesson does NOT cover

Retries with backoff — wrap a failing call in a retry loop. (Auto Intermediate.)
Idempotency — designing scripts that are safe to re-run. (Auto Intermediate.)
Specific error types per tool — Composio's full error taxonomy. (Auto Intermediate.)

For today: catch broadly, print a class name, move on.

Day 7 · ~11 min●

API calls can fail. Network drop, bad argument, expired auth token. Without a try/except, a failed call crashes your script.

python

try:
    result = toolset.execute_action(Action.GMAIL_FETCH_EMAILS, {"max_results": -1})
    print("ok")
except Exception as e:
    print(type(e).__name__)

Exception catches anything?

What kinds of errors does Composio throw?

`try/except` for tool calls

Network code is the natural home of try/except. Wrap every API call you can't guarantee will succeed:

python

try:
    result = toolset.execute_action(Action.GMAIL_FETCH_EMAILS, {"max_results": 5})
    messages = result.get("messages", [])
except Exception as e:
    print(f"Gmail fetch failed: {type(e).__name__}: {e}")
    messages = []    # graceful fallback

Catch broad to start, narrow as you learn

except Exception catches almost anything. As you get more specific, you might write:

python

except RuntimeError as e:
    # Composio's preferred error type
    ...
except ValueError as e:
    # bad argument shape
    ...

For a week-1 lesson, broad is fine. The platform's AUTH_REQUIRED flow is handled at a higher layer — your code won't see auth errors normally.

What `type(e).name` gives you

python

try:
    int("not a number")
except Exception as e:
    print(type(e).__name__)    # ValueError

Clean, single-word identification of the error class. Better for logs and quick diagnostics than the full message, which might include long stack traces.

What this lesson does NOT cover

Retries with backoff — wrap a failing call in a retry loop. (Auto Intermediate.)
Idempotency — designing scripts that are safe to re-run. (Auto Intermediate.)
Specific error types per tool — Composio's full error taxonomy. (Auto Intermediate.)

For today: catch broadly, print a class name, move on.

`try/except` for tool calls

Catch broad to start, narrow as you learn

What `type(e).name` gives you

What this lesson does NOT cover

`try/except` for tool calls

Catch broad to start, narrow as you learn

What `type(e).name` gives you

What this lesson does NOT cover

`try/except` for tool calls

Catch broad to start, narrow as you learn

What `type(e).name` gives you

What this lesson does NOT cover

Sign up to practice

`try/except` for tool calls

Catch broad to start, narrow as you learn

What `type(e).name` gives you

What this lesson does NOT cover

Sign up to practice

try/except for tool calls

Catch broad to start, narrow as you learn

What type(e).__name__ gives you

What this lesson does NOT cover

try/except for tool calls

Catch broad to start, narrow as you learn

What type(e).__name__ gives you

What this lesson does NOT cover

try/except for tool calls

Catch broad to start, narrow as you learn

What type(e).__name__ gives you

What this lesson does NOT cover

Sign up to practice

try/except for tool calls

Catch broad to start, narrow as you learn

What type(e).__name__ gives you

What this lesson does NOT cover

Sign up to practice

`try/except` for tool calls

What `type(e).name` gives you

`try/except` for tool calls

What `type(e).name` gives you

`try/except` for tool calls

What `type(e).name` gives you

`try/except` for tool calls

What `type(e).name` gives you