You can read your inbox, your calendar, your task list, your citations Sheet, and your draft paper. Each one works independently. What's missing between "I have these tools" and "I have a working Monday morning pipeline"?
The connections. Reading the Sheet and sending an email summary are separate function calls. The capstone chains them: read the Sheet, format a digest, send it to co-authors, and create a Calendar event for the next meeting.
Exactly. A workflow is a function that calls multiple actions in sequence, where the output of one feeds the input of the next. The pipeline has four steps: Sheets → format → Gmail, Calendar. By Friday that's a single function call — run_workflow.
What about the error handling? If the Sheet has no rows, or the Gmail send fails, does the whole pipeline crash?
That's Day 27 — safe_send wraps the send in a try/except that catches AUTH_REQUIRED errors and connection failures. The capstone calls safe_send instead of send_email directly, so partial failures return informative status dicts instead of crashing the whole run.
email_sheet_summary: read citations Sheet + send digest to co-authorsupcoming_to_tasks: find Calendar events + create a task per eventdoc_to_post: read a Docs summary + post to LinkedInsafe_send: wrap GMAIL_SEND_EMAIL in try/except for resilient pipelinesrun_workflow: the full literature-search pipeline capstoneGoal: a single function call that reads citations, emails the digest, and creates the next meeting event.
Create a free account to get started. Paid plans unlock all tracks.
You can read your inbox, your calendar, your task list, your citations Sheet, and your draft paper. Each one works independently. What's missing between "I have these tools" and "I have a working Monday morning pipeline"?
The connections. Reading the Sheet and sending an email summary are separate function calls. The capstone chains them: read the Sheet, format a digest, send it to co-authors, and create a Calendar event for the next meeting.
Exactly. A workflow is a function that calls multiple actions in sequence, where the output of one feeds the input of the next. The pipeline has four steps: Sheets → format → Gmail, Calendar. By Friday that's a single function call — run_workflow.
What about the error handling? If the Sheet has no rows, or the Gmail send fails, does the whole pipeline crash?
That's Day 27 — safe_send wraps the send in a try/except that catches AUTH_REQUIRED errors and connection failures. The capstone calls safe_send instead of send_email directly, so partial failures return informative status dicts instead of crashing the whole run.
email_sheet_summary: read citations Sheet + send digest to co-authorsupcoming_to_tasks: find Calendar events + create a task per eventdoc_to_post: read a Docs summary + post to LinkedInsafe_send: wrap GMAIL_SEND_EMAIL in try/except for resilient pipelinesrun_workflow: the full literature-search pipeline capstoneGoal: a single function call that reads citations, emails the digest, and creates the next meeting event.