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.

Insert a Follow-up Task into Google Tasks — Automation For Freelancers

Day 14 · ~12 min●

list_tasks from yesterday reads the task list. Today you write to it. Same safety principle as send_email and create_event: test with a task you can delete, confirm it appeared, then automate.

GOOGLETASKS_INSERT_TASK with list ID, title, and notes. The title is the task name; notes are the details.

Exactly. The function shape mirrors create_event — write action, ID, content fields, return the response dict. GOOGLETASKS_INSERT_TASK takes task_list_id, title, and notes. Check your Tasks app after the call and the task will be there:

python

result = toolset.execute_action(
    Action.GOOGLETASKS_INSERT_TASK,
    {
        "task_list_id": list_id,
        "title": "Follow up — Acme kickoff brief",
        "notes": "Send project brief by April 28. Confirm Zoom details."
    }
)
print(f"Task created: {result.get('id')}")

create_event from Day 12 had four fields. add_task has three. The shapes are similar but not identical. Do all write actions share a standard interface?

No — each action's parameter shape reflects the underlying Google API. create_event needs start and end datetimes; Tasks does not have times by default. Read each action's params when you use it for the first time. The Composio response format is consistent (always a dict); the input params vary by action.

So after create_event for the kickoff, I can call add_task to create the follow-up in one chained function. Calendar feeds Tasks.

That is exactly Week 4's upcoming_to_tasks function. Two actions, one pipeline:

python

def add_task(list_id: str, title: str, notes: str) -> dict:
    result = toolset.execute_action(
        Action.GOOGLETASKS_INSERT_TASK,
        {"task_list_id": list_id, "title": title, "notes": notes}
    )
    print(f"Task created: {result.get('id', 'ok')}")
    return result

Post-kickoff follow-up tasks now create themselves. I could wire my whole Monday morning in this.

Which task would you create automatically — the project brief request, the invoice reminder, or the status check halfway through?

Adding a Task to Google Tasks

GOOGLETASKS_INSERT_TASK creates a new task inside a task list:

python

result = toolset.execute_action(
    action=Action.GOOGLETASKS_INSERT_TASK,
    params={'taskListId': list_id, 'title': title, 'notes': notes}
)

Confirm the list exists first

Call list_tasks(list_id) before inserting to verify the target list exists. Inserting into a non-existent list raises an AUTH_REQUIRED or 404 error.

notes vs title: title is the one-line task name (visible in the task list). notes is the longer description (visible when you open the task). For client kickoffs, put the client name and project in title; add date, budget, and context in notes.

Day 14 · ~12 min●

list_tasks from yesterday reads the task list. Today you write to it. Same safety principle as send_email and create_event: test with a task you can delete, confirm it appeared, then automate.

GOOGLETASKS_INSERT_TASK with list ID, title, and notes. The title is the task name; notes are the details.

python

result = toolset.execute_action(
    Action.GOOGLETASKS_INSERT_TASK,
    {
        "task_list_id": list_id,
        "title": "Follow up — Acme kickoff brief",
        "notes": "Send project brief by April 28. Confirm Zoom details."
    }
)
print(f"Task created: {result.get('id')}")

create_event from Day 12 had four fields. add_task has three. The shapes are similar but not identical. Do all write actions share a standard interface?

So after create_event for the kickoff, I can call add_task to create the follow-up in one chained function. Calendar feeds Tasks.

That is exactly Week 4's upcoming_to_tasks function. Two actions, one pipeline:

python

def add_task(list_id: str, title: str, notes: str) -> dict:
    result = toolset.execute_action(
        Action.GOOGLETASKS_INSERT_TASK,
        {"task_list_id": list_id, "title": title, "notes": notes}
    )
    print(f"Task created: {result.get('id', 'ok')}")
    return result

Post-kickoff follow-up tasks now create themselves. I could wire my whole Monday morning in this.

Which task would you create automatically — the project brief request, the invoice reminder, or the status check halfway through?

Adding a Task to Google Tasks

GOOGLETASKS_INSERT_TASK creates a new task inside a task list:

python

result = toolset.execute_action(
    action=Action.GOOGLETASKS_INSERT_TASK,
    params={'taskListId': list_id, 'title': title, 'notes': notes}
)

Confirm the list exists first

Call list_tasks(list_id) before inserting to verify the target list exists. Inserting into a non-existent list raises an AUTH_REQUIRED or 404 error.

result = toolset.execute_action( Action.GOOGLETASKS_INSERT_TASK, { "task_list_id": list_id, "title": "Follow up — Acme kickoff brief", "notes": "Send project brief by April 28. Confirm Zoom details." } ) print(f"Task created: {result.get('id')}")

def add_task(list_id: str, title: str, notes: str) -> dict: result = toolset.execute_action( Action.GOOGLETASKS_INSERT_TASK, {"task_list_id": list_id, "title": title, "notes": notes} ) print(f"Task created: {result.get('id', 'ok')}") return result

Adding a Task to Google Tasks

GOOGLETASKS_INSERT_TASK creates a new task inside a task list:

python

result = toolset.execute_action(
    action=Action.GOOGLETASKS_INSERT_TASK,
    params={'taskListId': list_id, 'title': title, 'notes': notes}
)

Confirm the list exists first

Call list_tasks(list_id) before inserting to verify the target list exists. Inserting into a non-existent list raises an AUTH_REQUIRED or 404 error.

Adding a Task to Google Tasks

GOOGLETASKS_INSERT_TASK creates a new task inside a task list:

python

result = toolset.execute_action(
    action=Action.GOOGLETASKS_INSERT_TASK,
    params={'taskListId': list_id, 'title': title, 'notes': notes}
)

Confirm the list exists first

Call list_tasks(list_id) before inserting to verify the target list exists. Inserting into a non-existent list raises an AUTH_REQUIRED or 404 error.

Adding a Task to Google Tasks

Confirm the list exists first

Adding a Task to Google Tasks

Confirm the list exists first

Adding a Task to Google Tasks

Confirm the list exists first

Sign up to practice

Adding a Task to Google Tasks

Confirm the list exists first

Sign up to practice