n8n calendar automation
Syncing Calendars across Accounts, using n8n
A practical walkthrough of using n8n to mirror busy time across multiple calendar accounts without exposing private event details.
Video
Calendar sync walkthrough
The Tella video explains the problem, the n8n workflow shape, and the choices that keep cross-account availability useful without leaking private event data.
n8n preview
Workflow preview
An inspectable n8n preview of the pattern: read source calendars, normalize events, decide create/update/delete actions, and write availability blocks into the target accounts.
Loading workflow preview...
Replay
Session Replay
A sanitized, self-contained replay of the build session for readers who want to inspect how the calendar-sync workflow was reasoned through and tested.
Blog
Keeping busy time in sync without sharing the details
Calendar sync gets awkward when work, client, and personal accounts all need to know when you are unavailable, but none of them should receive the full event title, attendee list, notes, or location from the others.
The n8n pattern here is to treat availability as the thing being synchronized, not the original event. The workflow lists events from each source calendar, filters out all-day or transparent entries, clips long events to the useful work window, then creates neutral busy blocks in the destination calendars.
The hard parts are not just API calls. The workflow also needs stable source markers, repeatable update/delete behavior, duplicate cleanup, and a way to test changes without publishing sensitive calendar data. That is why the artifacts here include the video, workflow preview, sanitized replay, and download slots separately.
Downloads
Downloadable assets
The reusable pieces: a scrubbed workflow export and a starter prompt for adapting the pattern.