Two weeks of pure reads. This week every function reads one API and writes into another — inbox becomes tasks, calendar becomes a sheet, emails become a digest you send to yourself. The skeleton is fetch, shape, write.
So each lesson still starts with execute_action on a read, but now ends with execute_action on a create or send? Two calls, inbound and outbound, and the body in between is the plumbing?
Exactly. Day 17 reads your first email and creates a task from it. Day 18 fetches emails and events then sends the digest to yourself. Day 19 finds an email by keyword and schedules a follow-up on your calendar. Day 20 loops over emails and creates one task per item. Day 21 is a three-step workflow: read, send, return the confirmation.
And every write lands in my real Gmail, Calendar, or Tasks? The test run actually creates the task or the event?
Live writes, every run, inside your own account. By Friday you'll have written five automations that read one thing and act on another — the first scripts that change state, not just observe it.
Goal: Shift from observing to acting — each function changes real state inside your account.
Create a free account to get started. Paid plans unlock all tracks.
Two weeks of pure reads. This week every function reads one API and writes into another — inbox becomes tasks, calendar becomes a sheet, emails become a digest you send to yourself. The skeleton is fetch, shape, write.
So each lesson still starts with execute_action on a read, but now ends with execute_action on a create or send? Two calls, inbound and outbound, and the body in between is the plumbing?
Exactly. Day 17 reads your first email and creates a task from it. Day 18 fetches emails and events then sends the digest to yourself. Day 19 finds an email by keyword and schedules a follow-up on your calendar. Day 20 loops over emails and creates one task per item. Day 21 is a three-step workflow: read, send, return the confirmation.
And every write lands in my real Gmail, Calendar, or Tasks? The test run actually creates the task or the event?
Live writes, every run, inside your own account. By Friday you'll have written five automations that read one thing and act on another — the first scripts that change state, not just observe it.
Goal: Shift from observing to acting — each function changes real state inside your account.