The Calendar Nobody Looks At
Share on LinkedInMy family runs on Apple Calendar. We share iCloud calendars, and the shared Family calendar is where the household actually lives: practices, trips, appointments. If it isn’t on Family, it isn’t happening.
I barely use Google Calendar. But my personal email is Gmail. When I book a hotel, a flight, or a haircut, the confirmation lands in Gmail, and Google quietly adds an event to my Google Calendar. Meeting invites sent to that address land there too. Which means the bookings that matter most to my family, like the hotel for a tournament weekend, live in a calendar nobody in the family looks at. Me included.
So I recreated them by hand. Every hotel stay and every flight, retyped into Family one at a time. And when a booking changed in Google, I had to notice, then go fix the copy too. Two sources of truth is the same as none, and the manual one is always a step behind.
What I wanted
I wrote the requirements down before anything got built, because this is the kind of problem where “sort of works” is worse than nothing:
- One way. Google to iCloud. Google stays the source and is never written to.
- Everything lands in my Personal iCloud calendar. A haircut lands there and stays there.
- Promote by dragging. If I drag a hotel stay into Family in Apple Calendar, the sync follows it. If the dates change in Google later, the Family copy updates. If the booking is cancelled, it disappears from Family. No duplicates, ever.
- Deleted means deleted. If I delete a copy, the sync never “helpfully” puts it back.
- Today forward. No backfilling years of history.
- $0 a month, and it can’t depend on my Mac being awake.
The third one is the whole point. Promoting an event to the family has to happen where the family already lives, with the gesture everyone already knows. Not in some settings page in Google.
Why nothing off the shelf worked
I looked first. Building should be the last resort, not the first instinct.
- Commercial sync services are trial-only or paid. The free tiers sync manually or once a month.
- Automation platforms either can’t write to iCloud at all, or only handle new events. No updates, no cancellations, polling hourly.
- Subscribing to Google’s private calendar feed gives you a separate, read-only calendar. You can’t drag anything out of it.
- The closest open-source sync tool brings back copies you deleted the next time the source event changes.
Every one of them failed the same way. None of them kept a memory of “this copy was moved” or “this copy was deleted on purpose.” That memory turned out to be the entire problem.
Research first, then a second opinion
I had Claude Code run a deep research pass on the Google Calendar API, iCloud’s CalDAV interface, and Cloudflare Workers’ free-tier limits. Then I asked for a second pass with a different job: red-team the plan, and look for anything free that I’d missed.
The second pass earned its keep. My whole design rested on one assumption: when you drag an event to another calendar in Apple Calendar, it keeps its identity. Apple’s own developer documentation says an event’s identifier “most likely changes” when it moves. The research recommended designing around it. Reasonable advice, and it would have made the trickiest part of the system more complicated.
So instead of trusting the docs or building around them, we tested.
Testing reality instead of the docs
A handful of small experiments against my actual iCloud account, with throwaway test events:
- Can a script read and write my calendars, and tell which ones are shared? Yes.
- Drag a test event from Personal to Family on the Mac. It kept its unique ID, its file name, and a hidden tag we’d added.
- Same test on the iPhone. Same result.
- Does the family get notified? Yes. When an event appears in or leaves Family, everyone sharing it gets a notification. That’s normal shared-calendar behavior, and fine.
- Try to create a duplicate of an event that already exists in another calendar. iCloud refuses. A free, built-in duplicate guard I didn’t have to write.
- Formats. Timed events, all-day events, and multi-night hotel stays all display correctly, including across the daylight-saving change.
- Can a script running in Cloudflare’s cloud, not on my Mac, reach iCloud? Yes.
The documentation was more cautious than reality, in my favor. The part of the design I expected to be fragile turned into the simplest part. If I’d trusted the docs, I’d have built something more complicated to solve a problem that doesn’t exist.
What got built
A small Cloudflare Worker on the free plan. Every 15 minutes it asks Google only for what changed since the last run, turns each changed event into an iCloud calendar entry, and writes new ones to my Personal calendar.
A few decisions do most of the work:
- Every copy gets a predictable identity derived from the Google event. Re-running is always safe, and a crash halfway through can’t create duplicates.
- It follows the drag. If a copy is no longer in Personal, the sync checks Family for the same identity and keeps updating it there. If it’s in neither calendar, it concludes I deleted it and never recreates it.
- The memory lives in a tiny database inside a Cloudflare Durable Object: what was copied, where each copy lives now, and what I deleted. Only one sync can run at a time.
- Privacy by default. Copies are marked private. Guest lists are stripped, so iCloud never emails invitations to anyone. For meeting invites, the video-call link gets pulled out and shown as a tappable link.
- Noise filtering. Contact birthdays, out-of-office blocks, and declined invites are skipped. My Google calendar had 155 upcoming events. 148 of them were contact birthdays.
- Safety brakes. If a run would delete an unusual number of events, or copies start vanishing in bulk, the sync pauses itself and waits for me.
- Alerts. A free uptime monitor emails me only if the sync reports an error or goes quiet for more than an hour.
It rolled out in gates. First a dry run that showed exactly what it would create. Then live sync limited to two meeting invites I’d approved. Then everything.
Cost: $0 a month.
The small stuff
A few moments that didn’t make the architecture diagram:
- A one-character bug. The first deploy couldn’t find my calendars. iCloud writes one attribute with single quotes where the code expected double quotes.
- A trade-off I reversed. I briefly moved the check to hourly to keep things light, then went back to 15 minutes. A booking showing up quickly matters more than the savings, and on the free plan both cost nothing.
- Credentials never passed through the conversation. Passwords and tokens went from the Mac’s Keychain straight into Cloudflare’s secret store. The AI built the plumbing without ever holding the keys.
The point
The judgment was mine. What “correct” meant for my family. Which requirement mattered most: dragging in Apple Calendar, not some workaround in Google. When to stop and test reality instead of trusting the documentation, or the research that trusted it.
What changed is how cheap everything around that judgment has become. The research, the testing, and the build were fast enough that I could ask for a second, skeptical round of research, run real experiments against my own account, and still ship the same day. Now a small, boring tool quietly fixes a daily annoyance for a whole household. The hotel shows up on Family. That’s the whole feature.
I write about building with AI and the Salesforce platform. Follow along on LinkedIn.
Share on LinkedIn