I finished Python Beginner. I can write small scripts. Where does this track go from there?
Two new layers. First, you learn to call tools — Gmail, Calendar, Slack, Sheets, Docs, Notion — from Python. Read your inbox, send a message, create an event, update a doc. Second, you learn the patterns that turn one-off tool calls into reliable scripts: idempotency, dedup, time windows, error handling, retries.
Tools? Like APIs?
Yes. We use Composio — one library that lets you call dozens of services through a single Python interface, toolset.execute_action(Action.<NAME>, {...}). You connect each service once (Gmail, Slack, etc.) and your scripts can read from it and write to it. By week 4 you'll write a script that reads from one tool, transforms with Python, and writes to another — the canonical automation shape.
What do I rate myself on below?
Rate where you are today. Most of these you haven't seen yet. Strongly disagree is a perfectly honest answer for now. The same prompts come back on day 30.
Automation Beginner builds on Python Beginner's primitives by adding one thing: the ability to make Python do things in the real world.
Week 1 — Tool primitives. Calling toolset.execute_action(Action.<NAME>, {...}). Reading the response (a dict). Iterating over a list response. Filtering with Python. Passing arguments. Handling tool errors.
Week 2 — Side effects. Sending email. Creating calendar events. Appending to Sheets/Docs. Updating items. Idempotency (safe re-run). Dedup (don't re-process the same thing twice).
Week 3 — Composition. Read from tool A, write to tool B. Filter then act. Time-window filtering. Errors across a chain. Step-by-step logging. A synthesis lesson that combines 4-5 primitives.
Week 4 — Production patterns. Retry on transient errors. Pagination (handling tools that return results in pages). Wrapping tool calls in your own helper functions. Batching across a list of items. Conditional dispatch (call A or B based on a flag). One final integration.
Write small Python scripts that read data from one service, transform it, and write to another — with retry, idempotency, and clear error messages. That foundation lets you stitch together any of the 100+ Composio-supported services into your own personal automations.
Python Beginner (or equivalent fluency). You should be comfortable with variables, lists, dicts, conditionals, for loops, functions, try/except, and reading files. Auto-Beg adds one new layer (Composio tool calls) on top of that kit.
Rate each statement honestly on the 1-5 scale. The same prompts come back on day 30 to mark your delta. No grade — just calibration.
I finished Python Beginner. I can write small scripts. Where does this track go from there?
Two new layers. First, you learn to call tools — Gmail, Calendar, Slack, Sheets, Docs, Notion — from Python. Read your inbox, send a message, create an event, update a doc. Second, you learn the patterns that turn one-off tool calls into reliable scripts: idempotency, dedup, time windows, error handling, retries.
Tools? Like APIs?
Yes. We use Composio — one library that lets you call dozens of services through a single Python interface, toolset.execute_action(Action.<NAME>, {...}). You connect each service once (Gmail, Slack, etc.) and your scripts can read from it and write to it. By week 4 you'll write a script that reads from one tool, transforms with Python, and writes to another — the canonical automation shape.
What do I rate myself on below?
Rate where you are today. Most of these you haven't seen yet. Strongly disagree is a perfectly honest answer for now. The same prompts come back on day 30.
Automation Beginner builds on Python Beginner's primitives by adding one thing: the ability to make Python do things in the real world.
Week 1 — Tool primitives. Calling toolset.execute_action(Action.<NAME>, {...}). Reading the response (a dict). Iterating over a list response. Filtering with Python. Passing arguments. Handling tool errors.
Week 2 — Side effects. Sending email. Creating calendar events. Appending to Sheets/Docs. Updating items. Idempotency (safe re-run). Dedup (don't re-process the same thing twice).
Week 3 — Composition. Read from tool A, write to tool B. Filter then act. Time-window filtering. Errors across a chain. Step-by-step logging. A synthesis lesson that combines 4-5 primitives.
Week 4 — Production patterns. Retry on transient errors. Pagination (handling tools that return results in pages). Wrapping tool calls in your own helper functions. Batching across a list of items. Conditional dispatch (call A or B based on a flag). One final integration.
Write small Python scripts that read data from one service, transform it, and write to another — with retry, idempotency, and clear error messages. That foundation lets you stitch together any of the 100+ Composio-supported services into your own personal automations.
Python Beginner (or equivalent fluency). You should be comfortable with variables, lists, dicts, conditionals, for loops, functions, try/except, and reading files. Auto-Beg adds one new layer (Composio tool calls) on top of that kit.
Rate each statement honestly on the 1-5 scale. The same prompts come back on day 30 to mark your delta. No grade — just calibration.
Create a free account to get started. Paid plans unlock all tracks.