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.

List Research Task Lists and Their Tasks — Automation For Researchers

Day 13 · ~12 min●

Your research task list has 15 to-dos from the last revision round. You want to build an automation that adds "Review new paper" tasks from the citation sheet. First you need the task list IDs. How do you get them?

find_events from Day 11 uses the calendar ID from list_calendars. For tasks, I'd expect a similar two-step: list the task lists first, then list the tasks inside a specific list.

Exactly right. First call GOOGLETASKS_LIST_TASK_LISTS to get your task lists — they're like notebooks, each with its own ID. Then call GOOGLETASKS_LIST_TASKS with a specific tasklist_id to get the tasks inside it:

python

list_result = toolset.execute_action(Action.GOOGLETASKS_LIST_TASK_LISTS, {})
task_lists = list_result.get("items", [])
# pick the list you want
task_result = toolset.execute_action(Action.GOOGLETASKS_LIST_TASKS, {"tasklist_id": list_id})
tasks = task_result.get("items", [])

What's a task list vs a task? I thought Google Tasks just had tasks.

Google Tasks has a two-level hierarchy: task lists are like research notebooks ("Paper Review", "Admin", "Writing"), and tasks live inside lists. GOOGLETASKS_LIST_TASK_LISTS returns the notebooks; GOOGLETASKS_LIST_TASKS returns the tasks inside one notebook. You need the list ID to access the tasks.

So I find the "Paper Review" task list by its title, grab its ID, then list the tasks inside it. The same lookup pattern as calendars.

The same pattern every time:

python

def list_tasks(list_id: str) -> list:
    task_result = toolset.execute_action(
        Action.GOOGLETASKS_LIST_TASKS,
        {"tasklist_id": list_id}
    )
    tasks = task_result.get("items", [])
    print(f"Found {len(tasks)} tasks in list")
    return tasks

I can see my entire "Paper Review" backlog from a Python function. That's the input to add_task on Day 14.

Tasks without a due date won't have a due field — use .get("due", "no date") when parsing. And the task status field is "needsAction" (not done) or "completed" — useful for filtering your active backlog from completed items.

Task List Hierarchy

Google Tasks has two levels:

Task lists — containers (like research notebooks)
Tasks — individual to-dos inside a list

python

# Step 1: get task list IDs
lists = toolset.execute_action(Action.GOOGLETASKS_LIST_TASK_LISTS, {})
task_lists = lists.get("items", [])

# Step 2: get tasks from a specific list
tasks_result = toolset.execute_action(
    Action.GOOGLETASKS_LIST_TASKS,
    {"tasklist_id": "your_list_id"}
)
tasks = tasks_result.get("items", [])

Task dict fields

Field	Meaning
`id`	Task ID for updating
`title`	Task name
`status`	`"needsAction"` or `"completed"`
`due`	Due date (may be absent)

Day 13 · ~12 min●

find_events from Day 11 uses the calendar ID from list_calendars. For tasks, I'd expect a similar two-step: list the task lists first, then list the tasks inside a specific list.

python

list_result = toolset.execute_action(Action.GOOGLETASKS_LIST_TASK_LISTS, {})
task_lists = list_result.get("items", [])
# pick the list you want
task_result = toolset.execute_action(Action.GOOGLETASKS_LIST_TASKS, {"tasklist_id": list_id})
tasks = task_result.get("items", [])

What's a task list vs a task? I thought Google Tasks just had tasks.

So I find the "Paper Review" task list by its title, grab its ID, then list the tasks inside it. The same lookup pattern as calendars.

The same pattern every time:

python

def list_tasks(list_id: str) -> list:
    task_result = toolset.execute_action(
        Action.GOOGLETASKS_LIST_TASKS,
        {"tasklist_id": list_id}
    )
    tasks = task_result.get("items", [])
    print(f"Found {len(tasks)} tasks in list")
    return tasks

I can see my entire "Paper Review" backlog from a Python function. That's the input to add_task on Day 14.

Task List Hierarchy

Google Tasks has two levels:

Task lists — containers (like research notebooks)
Tasks — individual to-dos inside a list

python

# Step 1: get task list IDs
lists = toolset.execute_action(Action.GOOGLETASKS_LIST_TASK_LISTS, {})
task_lists = lists.get("items", [])

# Step 2: get tasks from a specific list
tasks_result = toolset.execute_action(
    Action.GOOGLETASKS_LIST_TASKS,
    {"tasklist_id": "your_list_id"}
)
tasks = tasks_result.get("items", [])

Task dict fields

Field	Meaning
`id`	Task ID for updating
`title`	Task name
`status`	`"needsAction"` or `"completed"`
`due`	Due date (may be absent)

Task List Hierarchy

Task dict fields

Task List Hierarchy

Task dict fields

Task List Hierarchy

Task dict fields

Sign up to practice

Task List Hierarchy

Task dict fields

Sign up to practice