Three weeks of single-source functions. This week you combine them. What do you expect the shape of a cross-app function to look like?
Probably two or three toolset.execute_action calls back-to-back, feeding data from one into the next? Each call guarded with .get() and early returns so one empty result does not break the chain.
Exactly. The pattern is fetch, transform, write — repeat. Today you pull a Gmail subject, turn it into a Task. Later this week you pull events and write them to Sheets. Friday is a capstone morning report that touches three APIs in one call.
So by the end of the week I have one function that reads my inbox, checks my calendar, and writes a summary I can look at before my day starts?
One function, three APIs, one clean dict handed to the caller. That is the whole point of this track.
Goal: A script you can run every morning before your first coffee.
Create a free account to get started. Paid plans unlock all tracks.
Three weeks of single-source functions. This week you combine them. What do you expect the shape of a cross-app function to look like?
Probably two or three toolset.execute_action calls back-to-back, feeding data from one into the next? Each call guarded with .get() and early returns so one empty result does not break the chain.
Exactly. The pattern is fetch, transform, write — repeat. Today you pull a Gmail subject, turn it into a Task. Later this week you pull events and write them to Sheets. Friday is a capstone morning report that touches three APIs in one call.
So by the end of the week I have one function that reads my inbox, checks my calendar, and writes a summary I can look at before my day starts?
One function, three APIs, one clean dict handed to the caller. That is the whole point of this track.
Goal: A script you can run every morning before your first coffee.