Newsletter Automation Pipeline — Status Update

Completed: Full email + Google Drive integration for my client prospect with the “client Newsletter" automation system (using the WAT framework). We actually used client specific topics and reworked the graphic several times. Interestingly, Claude (actually maybe Nano Banana) demonstrates “fatigue” as more and more hallucinations! The newsletter started with a simple combination pie and bar chart, but it suddenly switched to an info graphic with all kinds of hallucinations embedded. We (Claude-code & I) couldn’t get it to revert to the simple graph, so I had to work around it.

***

What we built:

Email delivery via Gmail SMTP (tested & working)
Google Drive archival with OAuth token authentication (tested & working)
End-to-end orchestrator ready for production use

Speed bumps & how we resolved them:

OAuth Verification Blocker → Pivoted to Gmail App Passwords + SMTP for faster delivery (no verification delays)
Namespace Package Import Errors → Manually reorganized google-auth-oauthlib directory structure and updated imports to fix module resolution
Google Cloud Console Slowness → Patience + parallel setup (OAuth consent screen, test user, Drive API enablement all prepped while waiting)
Email Delivery Silent Failure → Found the issue: app password has spaces; SMTP requires no spaces. Added .replace(" ", "") to strip them before login.
Drive File Display Issue → Changed upload MIME type from text/html to text/plain so Google Drive shows the file as readable text instead of trying to edit it as a document.

The real win: Working with Claude Code for collaborative troubleshooting. Rather than Claude guessing, we iterated together—I described what I saw, Claude diagnosed the root cause, we tested fixes, and documented the learning. That cycle is way more effective than trying to solve it solo.

Next: Full end-to-end newsletter generation pipeline ready to test with real topics.

5 comments