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.

Handle AUTH_REQUIRED Errors with Try/Except — Automation For Entrepreneurs | zuzu.codes

Day 27 · ~12 min●

Your doc_to_post chains Docs and LinkedIn. But what if an OAuth token expires mid-workflow — Gmail returns AUTH_REQUIRED instead of a send confirmation? What happens to your capstone?

After doc_to_post I've been assuming the connections stay live. But OAuth tokens expire. If Gmail returns AUTH_REQUIRED during the capstone run, does the whole workflow crash?

Without error handling, yes — it crashes. With safe_send, the AUTH_REQUIRED case becomes a graceful status return instead of an exception. The capstone keeps running even if one email fails:

python

try:
    result = toolset.execute_action(Action.GMAIL_SEND_EMAIL, {"to": to, "subject": subject, "body": body})
    if "AUTH_REQUIRED" in str(result):
        return {"status": "auth_required", "to": to}
    return result
except Exception as e:
    return {"status": "error", "message": str(e)}

When does AUTH_REQUIRED appear? Is it an exception or a string in the response?

Composio surfaces AUTH_REQUIRED:<action_slug> as a string inside the response dict when OAuth fails — it's not a Python exception. So you check str(result) for the string instead of catching an exception. Here's the full function:

python

def safe_send(to: str, subject: str, body: str) -> dict:
    try:
        result = toolset.execute_action(Action.GMAIL_SEND_EMAIL, {"to": to, "subject": subject, "body": body})
        if "AUTH_REQUIRED" in str(result):
            print(f"Auth required — reconnect Gmail")
            return {"status": "auth_required", "to": to}
        print(f"Sent to {to}")
        return result
    except Exception as e:
        print(f"Send failed: {e}")
        return {"status": "error", "message": str(e)}

So the capstone can send 10 welcome emails and if one fails with AUTH_REQUIRED, the rest still go out. The workflow doesn't stop at the first error.

Fault-tolerant automation. That's the difference between a script that runs once and a tool you trust to run every Monday.

AUTH_REQUIRED is just an app asking you to log in again — expected, handled, not a crisis. That framing changes how I think about errors.

Log every failed send with the recipient address. When you reconnect the Gmail account and re-run, you need to know which sends to retry. {"status": "auth_required", "to": to} gives you exactly that.

Handling AUTH_REQUIRED

Composio surfaces AUTH_REQUIRED:<slug> as a string in the response when OAuth expires. Handling this gracefully keeps your capstone workflow alive even when a single token lapses mid-run.

python

result = toolset.execute_action(Action.GMAIL_SEND_EMAIL, {...})
if "AUTH_REQUIRED" in str(result):
    return {"status": "auth_required"}

Error handling flow

Call the action
Check for AUTH_REQUIRED in str(result)
Wrap in try/except Exception for unexpected errors
Return a status dict instead of crashing

Pitfall

Always log the failed recipient in the status dict. You need to know which sends to retry after reconnecting.

Sign up to practice

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

Day 27 · ~12 min●

Your doc_to_post chains Docs and LinkedIn. But what if an OAuth token expires mid-workflow — Gmail returns AUTH_REQUIRED instead of a send confirmation? What happens to your capstone?

After doc_to_post I've been assuming the connections stay live. But OAuth tokens expire. If Gmail returns AUTH_REQUIRED during the capstone run, does the whole workflow crash?

Without error handling, yes — it crashes. With safe_send, the AUTH_REQUIRED case becomes a graceful status return instead of an exception. The capstone keeps running even if one email fails:

python

try:
    result = toolset.execute_action(Action.GMAIL_SEND_EMAIL, {"to": to, "subject": subject, "body": body})
    if "AUTH_REQUIRED" in str(result):
        return {"status": "auth_required", "to": to}
    return result
except Exception as e:
    return {"status": "error", "message": str(e)}

When does AUTH_REQUIRED appear? Is it an exception or a string in the response?

python

def safe_send(to: str, subject: str, body: str) -> dict:
    try:
        result = toolset.execute_action(Action.GMAIL_SEND_EMAIL, {"to": to, "subject": subject, "body": body})
        if "AUTH_REQUIRED" in str(result):
            print(f"Auth required — reconnect Gmail")
            return {"status": "auth_required", "to": to}
        print(f"Sent to {to}")
        return result
    except Exception as e:
        print(f"Send failed: {e}")
        return {"status": "error", "message": str(e)}

So the capstone can send 10 welcome emails and if one fails with AUTH_REQUIRED, the rest still go out. The workflow doesn't stop at the first error.

Fault-tolerant automation. That's the difference between a script that runs once and a tool you trust to run every Monday.

AUTH_REQUIRED is just an app asking you to log in again — expected, handled, not a crisis. That framing changes how I think about errors.

Handling AUTH_REQUIRED

Composio surfaces AUTH_REQUIRED:<slug> as a string in the response when OAuth expires. Handling this gracefully keeps your capstone workflow alive even when a single token lapses mid-run.

python

result = toolset.execute_action(Action.GMAIL_SEND_EMAIL, {...})
if "AUTH_REQUIRED" in str(result):
    return {"status": "auth_required"}

Error handling flow

Call the action
Check for AUTH_REQUIRED in str(result)
Wrap in try/except Exception for unexpected errors
Return a status dict instead of crashing

Pitfall

Always log the failed recipient in the status dict. You need to know which sends to retry after reconnecting.