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.

Search for Google Spreadsheets by Name — Automation For Freelancers | zuzu.codes

Day 19 · ~12 min●

search_emails from Week 1 used a query string to find emails without knowing IDs upfront. The same search-by-name pattern applies to Sheets. What if you could find your time log by searching for "Time Log" instead of remembering the spreadsheet ID?

GOOGLESHEETS_SEARCH_SPREADSHEETS with a query string. Get back a list of matching spreadsheet dicts each with an ID I can use.

Exactly. Pass a query string and get back matching spreadsheets. Each dict has an id key you pass to read_range or append_row. No copying IDs from the URL bar:

python

result = toolset.execute_action(
    Action.GOOGLESHEETS_SEARCH_SPREADSHEETS,
    {"query": "Time Log"}
)
sheets = result.get("files", [])
for s in sheets:
    print(f"{s.get('id')}: {s.get('name')}")

The response key is "files" not "spreadsheets"? That is the third different key name this week.

Google Drive's API uses "files" as the generic resource list key. Sheets, Docs, and Slides are all Drive files under the hood. The Composio wrapper surfaces the Drive response shape — which uses "files". Same safe .get() reflex, different key name.

So I search for my time log by name, get the ID, and pass it to append_row. No hardcoded IDs in my automation script.

A dynamic pipeline. Name changes? Just change the search query:

python

def search_sheets(query: str) -> list:
    result = toolset.execute_action(
        Action.GOOGLESHEETS_SEARCH_SPREADSHEETS,
        {"query": query}
    )
    sheets = result.get("files", [])
    print(f"Found {len(sheets)} sheets matching '{query}'")
    return sheets

My script now finds my time log by name instead of hardcoded ID. It will survive a rename.

One caveat: query matching is fuzzy. "Time Log" might return multiple spreadsheets — "Time Log 2025", "Time Log 2026", "Archive — Time Log". Always inspect sheets[0] before assuming you have the right one.

Searching Google Sheets

GOOGLESHEETS_SEARCH_SPREADSHEETS finds spreadsheets by name — useful when you have many files and need to locate the right one programmatically:

python

result = toolset.execute_action(
    action=Action.GOOGLESHEETS_SEARCH_SPREADSHEETS,
    params={'query': query}
)
sheets = result.get('spreadsheets', [])

Using the search result

Each spreadsheet dict includes spreadsheetId — the ID you need for read_range and append_row. Searching by name ('Time Log') is more robust than hardcoding a spreadsheet ID that could change when a file is replaced.

Pattern: search → get ID → read or write. This is the same discover-then-act pattern as list_calendars → find_events.

Sign up to practice

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

Day 19 · ~12 min●

GOOGLESHEETS_SEARCH_SPREADSHEETS with a query string. Get back a list of matching spreadsheet dicts each with an ID I can use.

Exactly. Pass a query string and get back matching spreadsheets. Each dict has an id key you pass to read_range or append_row. No copying IDs from the URL bar:

python

result = toolset.execute_action(
    Action.GOOGLESHEETS_SEARCH_SPREADSHEETS,
    {"query": "Time Log"}
)
sheets = result.get("files", [])
for s in sheets:
    print(f"{s.get('id')}: {s.get('name')}")

The response key is "files" not "spreadsheets"? That is the third different key name this week.

So I search for my time log by name, get the ID, and pass it to append_row. No hardcoded IDs in my automation script.

A dynamic pipeline. Name changes? Just change the search query:

python

def search_sheets(query: str) -> list:
    result = toolset.execute_action(
        Action.GOOGLESHEETS_SEARCH_SPREADSHEETS,
        {"query": query}
    )
    sheets = result.get("files", [])
    print(f"Found {len(sheets)} sheets matching '{query}'")
    return sheets

My script now finds my time log by name instead of hardcoded ID. It will survive a rename.

Searching Google Sheets

GOOGLESHEETS_SEARCH_SPREADSHEETS finds spreadsheets by name — useful when you have many files and need to locate the right one programmatically:

python

result = toolset.execute_action(
    action=Action.GOOGLESHEETS_SEARCH_SPREADSHEETS,
    params={'query': query}
)
sheets = result.get('spreadsheets', [])

Using the search result

Pattern: search → get ID → read or write. This is the same discover-then-act pattern as list_calendars → find_events.