You finished the Python track. You can compute stats and write reusable functions. Now: your literature search still happens manually, your co-author emails are still typed by hand, and your paper deadlines still live only in your head. What would happen if all of that ran on its own?
I'd probably catch more papers I'm missing. And stop sending the same "have you seen this?" email five times.
Exactly. This track connects Python to the apps your research already runs on — Gmail, Sheets, Calendar. Rate yourself on six automation skills before we wire the first connection.
I've never used an API for anything outside of R packages. Is this the same thing?
Similar idea, much more control. Rate honestly — a 1 on everything is a perfectly valid starting point. Day 30 answers will show how far you've moved.
Thirty days. One real project: a literature-search pipeline. By Day 28 you'll have a workflow that reads a candidate-citations Sheet, drafts an email to co-authors summarising the top 5 new hits, and creates a Calendar event for the next literature-review meeting.
| Week | Focus | Research framing |
|---|---|---|
| 1 | Gmail read, search, draft, send | "Draft an email to co-authors with 'revision round N' subject." |
| 2 | Calendar, Tasks | "Create a Calendar event for every journal deadline." |
| 3 | Sheets, Docs | "Append each literature hit to a shared Sheet of candidate citations." |
| 4 | Cross-app workflows, capstone | "Wire the full literature-search pipeline." |
Every lesson uses live connections to your actual accounts. Tests check data shapes, not fixed values.
Create a free account to get started. Paid plans unlock all tracks.
You finished the Python track. You can compute stats and write reusable functions. Now: your literature search still happens manually, your co-author emails are still typed by hand, and your paper deadlines still live only in your head. What would happen if all of that ran on its own?
I'd probably catch more papers I'm missing. And stop sending the same "have you seen this?" email five times.
Exactly. This track connects Python to the apps your research already runs on — Gmail, Sheets, Calendar. Rate yourself on six automation skills before we wire the first connection.
I've never used an API for anything outside of R packages. Is this the same thing?
Similar idea, much more control. Rate honestly — a 1 on everything is a perfectly valid starting point. Day 30 answers will show how far you've moved.
Thirty days. One real project: a literature-search pipeline. By Day 28 you'll have a workflow that reads a candidate-citations Sheet, drafts an email to co-authors summarising the top 5 new hits, and creates a Calendar event for the next literature-review meeting.
| Week | Focus | Research framing |
|---|---|---|
| 1 | Gmail read, search, draft, send | "Draft an email to co-authors with 'revision round N' subject." |
| 2 | Calendar, Tasks | "Create a Calendar event for every journal deadline." |
| 3 | Sheets, Docs | "Append each literature hit to a shared Sheet of candidate citations." |
| 4 | Cross-app workflows, capstone | "Wire the full literature-search pipeline." |
Every lesson uses live connections to your actual accounts. Tests check data shapes, not fixed values.