Weeks 1 through 3 gave you 15 actions across 5 apps. Each was a single API call, a single result. What changes in Week 4?
We chain them. The output of one action becomes the input to the next. search_sheets gives the ID → read_range reads the rows → send_email sends the summary.
That's the workflow pattern exactly. Actions were nouns — an email, an event, a row. Workflows are verbs strung together — read-then-send, find-then-add, read-doc-then-post. The function calls don't change. What changes is that you write one Python function that calls two or three of them in sequence.
And each sub-call still returns a dict — I just pass the right key from one result into the next params dict.
That's all it is. The capstone on Day 28 chains three apps in one function: Sheets gives you the data, Gmail drafts the advisor email, Calendar creates the deadline event. Nothing you haven't done individually. The only new skill is sequencing and extracting the right key at each step.
Create a free account to get started. Paid plans unlock all tracks.
Weeks 1 through 3 gave you 15 actions across 5 apps. Each was a single API call, a single result. What changes in Week 4?
We chain them. The output of one action becomes the input to the next. search_sheets gives the ID → read_range reads the rows → send_email sends the summary.
That's the workflow pattern exactly. Actions were nouns — an email, an event, a row. Workflows are verbs strung together — read-then-send, find-then-add, read-doc-then-post. The function calls don't change. What changes is that you write one Python function that calls two or three of them in sequence.
And each sub-call still returns a dict — I just pass the right key from one result into the next params dict.
That's all it is. The capstone on Day 28 chains three apps in one function: Sheets gives you the data, Gmail drafts the advisor email, Calendar creates the deadline event. Nothing you haven't done individually. The only new skill is sequencing and extracting the right key at each step.