Drafts as Hub- How AI Helped Me Connect Five Apps on iPad -Part 4
What broke, what I compromised on, what I built and never use.
If you’ve made it this far in the series, you’ve seen the version of my workflow that works. The Daily Log that hits three destinations with one tap. The Cloudflare Workers that let my iPad reach services it shouldn’t be able to. The morning briefing that reads my day to me through AirPods. It all sounds clean and intentional when I describe it in sequence.
This part is about the mess behind that. What broke, what I compromised on, what I built and never use, and what still isn’t solved. I think this might be the most useful part of the series because anyone building something like this will hit the same walls, and knowing where they are saves time.
The Meeting Notes Problem
Meeting notes were the workflow that humbled me. The idea was straightforward - I capture meeting notes in Notion during the meeting, and then the system syncs those notes to Apple Notes and Obsidian so I can access them from any device. Same multi-destination philosophy as everything else in this series.
I started building this in Drafts. Five actions and two Shortcuts. The logic wasn’t that different from my Daily Log or Weekly Note actions - capture content, format it, route it to multiple destinations. But meeting notes are structurally more complex than daily bullets. They have agendas, meeting notes sections, and AI-generated meeting summaries. The formatting requirements for each destination are different. And unlike my other actions where I’m the one triggering them manually, I wanted the meeting note sync to run automatically every weekday morning.
The rest of this article is for paid subscribers. If you want the honest breakdown of what broke, what compromises I’m still living with, and what I’d tell someone before they build a system like this, subscribe below.
