You can send and read Gmail from code now. But a freelancer's workflow spans more than email — kickoff calls in Calendar, follow-up tasks in Google Tasks. What if creating a Calendar event when a client confirms required no tab-switching?
Right now I copy the client's email, open Calendar, create the event, copy the Zoom link, add it to Tasks. Four apps, ten minutes, every new project.
This week Python handles that chain. GOOGLECALENDAR_LIST_CALENDARS shows you which calendars are available. GOOGLECALENDAR_FIND_EVENT searches for upcoming calls. GOOGLECALENDAR_CREATE_EVENT creates the kickoff. GOOGLETASKS_LIST_TASKS and GOOGLETASKS_INSERT_TASK manage the follow-up. One function call per step.
And the Calendar and Tasks data shapes are similar to Gmail?
Same pattern every time — call an action, parse a dict, extract what you need with .get(). The apps are different; the Python shape is identical.
list_calendars: list all available Google Calendar calendarsfind_events: search for upcoming events in a specific calendarcreate_event: create a client kickoff event with start/end timeslist_tasks: list available task lists and their tasksadd_task: insert a follow-up task into a task listGoal: by the end of the week you can auto-schedule a client kickoff the moment a project is confirmed.
Create a free account to get started. Paid plans unlock all tracks.
You can send and read Gmail from code now. But a freelancer's workflow spans more than email — kickoff calls in Calendar, follow-up tasks in Google Tasks. What if creating a Calendar event when a client confirms required no tab-switching?
Right now I copy the client's email, open Calendar, create the event, copy the Zoom link, add it to Tasks. Four apps, ten minutes, every new project.
This week Python handles that chain. GOOGLECALENDAR_LIST_CALENDARS shows you which calendars are available. GOOGLECALENDAR_FIND_EVENT searches for upcoming calls. GOOGLECALENDAR_CREATE_EVENT creates the kickoff. GOOGLETASKS_LIST_TASKS and GOOGLETASKS_INSERT_TASK manage the follow-up. One function call per step.
And the Calendar and Tasks data shapes are similar to Gmail?
Same pattern every time — call an action, parse a dict, extract what you need with .get(). The apps are different; the Python shape is identical.
list_calendars: list all available Google Calendar calendarsfind_events: search for upcoming events in a specific calendarcreate_event: create a client kickoff event with start/end timeslist_tasks: list available task lists and their tasksadd_task: insert a follow-up task into a task listGoal: by the end of the week you can auto-schedule a client kickoff the moment a project is confirmed.