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.

Pagination — Automation Foundations

Day 24 · ~11 min●

A Composio call asks for N results — say max_results=10. The tool returns 10 messages and a nextPageToken. To get all messages, you keep calling, passing the token each time, until the token is empty.

The pattern is a while loop with the page token as the loop variable:

python

all_messages = []
page_token = None

while True:
    args = {"max_results": 10}
    if page_token:
        args["page_token"] = page_token
    result = toolset.execute_action(Action.GMAIL_FETCH_EMAILS, args)
    page = result.get("messages", [])
    all_messages.extend(page)
    page_token = result.get("nextPageToken")
    if not page_token:
        break

print(f"got {len(all_messages)} total messages")

What stops it from looping forever?

Two things. (1) The tool eventually returns no nextPageToken (you've consumed all pages) — break. (2) For safety, cap the iteration count yourself in production scripts:

python

for _ in range(50):    # at most 50 pages × 10 = 500 messages
    ...
    if not page_token:
        break

Protects against bugs where the token never goes empty.

Some APIs use offsets instead of tokens, right?

Yes — ?offset=0&limit=10, ?offset=10&limit=10, etc. Same pattern, different variable. Loop until you get back fewer than limit items, or until offset exceeds a known total.

Pagination — token-based

Many APIs return a page of results plus a token to fetch the next page. The loop:

python

all_items = []
page_token = None

while True:
    args = {"max_results": 10}
    if page_token:
        args["page_token"] = page_token
    
    result = SOME_CALL(args)
    
    page = result.get("items", [])
    all_items.extend(page)
    
    page_token = result.get("nextPageToken")
    if not page_token:
        break

Why pages instead of returning everything

Latency: 10 results comes back in ms; 10,000 takes seconds and might time out.
Memory: 10 results fit in RAM; 100,000 might not.
Rate limits: APIs charge per call, but also enforce per-call result caps.

Pagination shapes you'll see

Style	Tool	How
Token	Gmail, Drive, Notion	Pass `page_token` from prev response
Offset/limit	Many REST APIs	Pass `?offset=N&limit=M` until short page
Cursor	Some GraphQL APIs	Pass `after` cursor
Page number	Older APIs	Pass `page=1`, `page=2`, ...

Composio normalises some of this for you — check the action docs to see which arg names apply.

Always cap the loop

python

MAX_PAGES = 100
for _ in range(MAX_PAGES):
    ...
    if not page_token:
        break
else:
    print(f"warning: hit MAX_PAGES — there may be more results")

Defence against bugs where the token never empties. The else runs only if no break happened — useful diagnostic.

Stop early when you've found what you need

If you're searching for a specific item, break as soon as you find it. No need to fetch every page.

python

for page in pages:
    for msg in page:
        if msg["subject"] == target:
            return msg    # found it
# falls off the end → not found

Day 24 · ~11 min●

The pattern is a while loop with the page token as the loop variable:

python

all_messages = []
page_token = None

while True:
    args = {"max_results": 10}
    if page_token:
        args["page_token"] = page_token
    result = toolset.execute_action(Action.GMAIL_FETCH_EMAILS, args)
    page = result.get("messages", [])
    all_messages.extend(page)
    page_token = result.get("nextPageToken")
    if not page_token:
        break

print(f"got {len(all_messages)} total messages")

What stops it from looping forever?

Two things. (1) The tool eventually returns no nextPageToken (you've consumed all pages) — break. (2) For safety, cap the iteration count yourself in production scripts:

python

for _ in range(50):    # at most 50 pages × 10 = 500 messages
    ...
    if not page_token:
        break

Protects against bugs where the token never goes empty.

Some APIs use offsets instead of tokens, right?

Yes — ?offset=0&limit=10, ?offset=10&limit=10, etc. Same pattern, different variable. Loop until you get back fewer than limit items, or until offset exceeds a known total.

Pagination — token-based

Many APIs return a page of results plus a token to fetch the next page. The loop:

python

all_items = []
page_token = None

while True:
    args = {"max_results": 10}
    if page_token:
        args["page_token"] = page_token
    
    result = SOME_CALL(args)
    
    page = result.get("items", [])
    all_items.extend(page)
    
    page_token = result.get("nextPageToken")
    if not page_token:
        break

Why pages instead of returning everything

Latency: 10 results comes back in ms; 10,000 takes seconds and might time out.
Memory: 10 results fit in RAM; 100,000 might not.
Rate limits: APIs charge per call, but also enforce per-call result caps.

Pagination shapes you'll see

Style	Tool	How
Token	Gmail, Drive, Notion	Pass `page_token` from prev response
Offset/limit	Many REST APIs	Pass `?offset=N&limit=M` until short page
Cursor	Some GraphQL APIs	Pass `after` cursor
Page number	Older APIs	Pass `page=1`, `page=2`, ...

Composio normalises some of this for you — check the action docs to see which arg names apply.

Always cap the loop

python

MAX_PAGES = 100
for _ in range(MAX_PAGES):
    ...
    if not page_token:
        break
else:
    print(f"warning: hit MAX_PAGES — there may be more results")

Defence against bugs where the token never empties. The else runs only if no break happened — useful diagnostic.

Stop early when you've found what you need

If you're searching for a specific item, break as soon as you find it. No need to fetch every page.

python

for page in pages:
    for msg in page:
        if msg["subject"] == target:
            return msg    # found it
# falls off the end → not found

Why pages instead of returning everything

Pagination shapes you'll see

Always cap the loop

Stop early when you've found what you need

Why pages instead of returning everything

Pagination shapes you'll see

Always cap the loop

Stop early when you've found what you need

Why pages instead of returning everything

Pagination shapes you'll see

Always cap the loop

Stop early when you've found what you need

Sign up to practice

Why pages instead of returning everything

Pagination shapes you'll see

Always cap the loop

Stop early when you've found what you need

Sign up to practice