You've written Python scripts. Now the question is: can those scripts talk to your actual apps — Gmail, Sheets, Calendar? Before we wire anything up, tell me — what's the most repetitive thing you do for your research every week?
I email my advisor the same weekly update, update a shared Sheet manually, then add a calendar event for next week's check-in. Three separate steps, every Friday.
By Day 28 that's a single function call. But first — rate yourself honestly on six skills. This is a snapshot of where you are, not a test.
I'm comfortable with basic Python. APIs and OAuth feel like a different world though.
APIs are just functions with a longer address. OAuth is just a permission slip your app signs. Rate where you actually are and we'll close the gaps one day at a time.
Thirty days. One real project: a research-progress tracker. By Day 28 you'll have a workflow that reads this week's entries from a progress Sheet, drafts an email summary to your advisor, and creates a Calendar event for the next check-in — all in one function call.
| Week | Focus | Student framing |
|---|---|---|
| 1 | Gmail — read, search, draft, send | "Draft the weekly advisor update without touching Gmail." |
| 2 | Calendar + Tasks | "Create the deadline event from your syllabus entry automatically." |
| 3 | Sheets + Docs | "Append the lab session row; pull the research doc." |
| 4 | Cross-app workflows + capstone | "One function: read Sheet → email advisor → schedule next check-in." |
Every lesson connects to your actual Google account via Composio.
Create a free account to get started. Paid plans unlock all tracks.
You've written Python scripts. Now the question is: can those scripts talk to your actual apps — Gmail, Sheets, Calendar? Before we wire anything up, tell me — what's the most repetitive thing you do for your research every week?
I email my advisor the same weekly update, update a shared Sheet manually, then add a calendar event for next week's check-in. Three separate steps, every Friday.
By Day 28 that's a single function call. But first — rate yourself honestly on six skills. This is a snapshot of where you are, not a test.
I'm comfortable with basic Python. APIs and OAuth feel like a different world though.
APIs are just functions with a longer address. OAuth is just a permission slip your app signs. Rate where you actually are and we'll close the gaps one day at a time.
Thirty days. One real project: a research-progress tracker. By Day 28 you'll have a workflow that reads this week's entries from a progress Sheet, drafts an email summary to your advisor, and creates a Calendar event for the next check-in — all in one function call.
| Week | Focus | Student framing |
|---|---|---|
| 1 | Gmail — read, search, draft, send | "Draft the weekly advisor update without touching Gmail." |
| 2 | Calendar + Tasks | "Create the deadline event from your syllabus entry automatically." |
| 3 | Sheets + Docs | "Append the lab session row; pull the research doc." |
| 4 | Cross-app workflows + capstone | "One function: read Sheet → email advisor → schedule next check-in." |
Every lesson connects to your actual Google account via Composio.