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.

Create a Task: Writing to Google Tasks — Automation For Beginners

Day 14 · ~12 min●

You know how to list tasks. Time to add one from Python. What do you think the params look like?

Probably a title at minimum? And maybe a status like needsAction to mark it incomplete?

Exactly. GOOGLETASKS_INSERT_TASK takes a title, an optional status, and a tasklist_id. For the default list, passing the string "@default" works — Google maps that to your primary list automatically:

python

result = toolset.execute_action(Action.GOOGLETASKS_INSERT_TASK, {
    "title": "Review PR",
    "tasklist_id": "@default",
    "status": "needsAction",
})

@default is a magic string the API recognizes? Instead of a real list ID?

Google uses that token for "whatever the user's default list is." Saves you a lookup call just to find your own primary list. Every Google client treats the magic token identically, so the same three lines work whether you have one list or ten. The function stays short:

python

def create_task(title: str) -> dict:
    result = toolset.execute_action(Action.GOOGLETASKS_INSERT_TASK, {
        "title": title,
        "tasklist_id": "@default",
        "status": "needsAction",
    })
    return result

Why hard-code "needsAction" instead of letting the caller pass a status?

A newly created task is virtually always open — "needsAction" is the safe default. You can always add a status parameter later. Starting with the common case keeps the function's signature small and the caller's life simple.

So once this runs, the task actually shows up in Google Tasks on my phone within seconds?

Phone, web, any Google client. You just wrote your name onto Google's servers. Every function from here that touches Tasks uses this same three-line skeleton.

Writing to Tasks

TL;DR: GOOGLETASKS_INSERT_TASK needs a title, a tasklist_id, and a status — pass "@default" to aim at your primary list without any lookup.

Action enum — Action.GOOGLETASKS_INSERT_TASK
Magic token — "@default" maps to the user's primary task list
Status default — "needsAction" marks the task as still open
Return dict — includes the new task's id, title, status

Task statuses

Value	Meaning
`needsAction`	open / to-do
`completed`	done, tucked under the strikethrough

Day 14 · ~12 min●

You know how to list tasks. Time to add one from Python. What do you think the params look like?

Probably a title at minimum? And maybe a status like needsAction to mark it incomplete?

python

result = toolset.execute_action(Action.GOOGLETASKS_INSERT_TASK, {
    "title": "Review PR",
    "tasklist_id": "@default",
    "status": "needsAction",
})

@default is a magic string the API recognizes? Instead of a real list ID?

python

def create_task(title: str) -> dict:
    result = toolset.execute_action(Action.GOOGLETASKS_INSERT_TASK, {
        "title": title,
        "tasklist_id": "@default",
        "status": "needsAction",
    })
    return result

Why hard-code "needsAction" instead of letting the caller pass a status?

So once this runs, the task actually shows up in Google Tasks on my phone within seconds?

Phone, web, any Google client. You just wrote your name onto Google's servers. Every function from here that touches Tasks uses this same three-line skeleton.

Writing to Tasks

TL;DR: GOOGLETASKS_INSERT_TASK needs a title, a tasklist_id, and a status — pass "@default" to aim at your primary list without any lookup.

Action enum — Action.GOOGLETASKS_INSERT_TASK
Magic token — "@default" maps to the user's primary task list
Status default — "needsAction" marks the task as still open
Return dict — includes the new task's id, title, status

Task statuses

Value	Meaning
`needsAction`	open / to-do
`completed`	done, tucked under the strikethrough

def create_task(title: str) -> dict: result = toolset.execute_action(Action.GOOGLETASKS_INSERT_TASK, { "title": title, "tasklist_id": "@default", "status": "needsAction", }) return result

Writing to Tasks

TL;DR: GOOGLETASKS_INSERT_TASK needs a title, a tasklist_id, and a status — pass "@default" to aim at your primary list without any lookup.

Action enum — Action.GOOGLETASKS_INSERT_TASK

Magic token — "@default" maps to the user's primary task list

Status default — "needsAction" marks the task as still open

Return dict — includes the new task's id, title, status

Task statuses

Value	Meaning
`needsAction`	open / to-do
`completed`	done, tucked under the strikethrough

def create_task(title: str) -> dict: result = toolset.execute_action(Action.GOOGLETASKS_INSERT_TASK, { "title": title, "tasklist_id": "@default", "status": "needsAction", }) return result

Writing to Tasks

TL;DR: GOOGLETASKS_INSERT_TASK needs a title, a tasklist_id, and a status — pass "@default" to aim at your primary list without any lookup.

Action enum — Action.GOOGLETASKS_INSERT_TASK

Magic token — "@default" maps to the user's primary task list

Status default — "needsAction" marks the task as still open

Return dict — includes the new task's id, title, status

Task statuses

Value	Meaning
`needsAction`	open / to-do
`completed`	done, tucked under the strikethrough

Writing to Tasks

Task statuses

Writing to Tasks

Task statuses

Writing to Tasks

Task statuses

Sign up to practice

Writing to Tasks

Task statuses

Sign up to practice