Last week the target was Gmail. This week it is your Calendar and Tasks. Same toolset.execute_action skeleton, different action enums. What's the first question you would ask about either API?
Probably the shape of a calendar event. Is it a dict like an email, with fields like summary and start?
Almost exactly. A Google Calendar event is a dict with keys like summary, start, end, location. Google Tasks are even simpler — title, status, due. The same Python skeleton reads both: call the action, .get() the items list, pull the field you want.
So every function I wrote last week carries over? The Gmail muscle applies directly to Calendar and Tasks?
Every line of Week 1 transfers. By Friday you will count calendars, find events, create events, list tasks, and create tasks — all with the exact same three-line skeleton.
GOOGLECALENDAR_FIND_EVENTGoal: Apply the Gmail skeleton to two new APIs without looking anything up.
Create a free account to get started. Paid plans unlock all tracks.
Last week the target was Gmail. This week it is your Calendar and Tasks. Same toolset.execute_action skeleton, different action enums. What's the first question you would ask about either API?
Probably the shape of a calendar event. Is it a dict like an email, with fields like summary and start?
Almost exactly. A Google Calendar event is a dict with keys like summary, start, end, location. Google Tasks are even simpler — title, status, due. The same Python skeleton reads both: call the action, .get() the items list, pull the field you want.
So every function I wrote last week carries over? The Gmail muscle applies directly to Calendar and Tasks?
Every line of Week 1 transfers. By Friday you will count calendars, find events, create events, list tasks, and create tasks — all with the exact same three-line skeleton.
GOOGLECALENDAR_FIND_EVENTGoal: Apply the Gmail skeleton to two new APIs without looking anything up.