Bot: synced content calendar

Copying dates by hand from the planning sheet to the calendar is the job that always gets postponed, and when it gets postponed the calendar lies. This bot keeps it synced: new items show up, canceled ones disappear, and changes propagate. ## By the numbers - Runs **once a day**, overnight: a content calendar does not change by the minute and over-syncing creates junk notifications. - Syncs **3 types of change**: additions, removals and edits. Removal is the one almost everyone forgets, and it is the one that makes the calendar stop being trustworthy. - The **first run is compared by hand** with both calendars open, before you give it permission to delete anything. ## The prompt ``` Set up a new bot with a daily run. Guide me to connect the source where I plan content (Notion, Google Sheets or Airtable) and the calendar where I want to see it, and then configure it: 1. Anything new in the source shows up in the calendar. 2. Anything canceled in the source is deleted from the calendar. 3. Changes of date, time or local time propagate. 4. Each calendar event carries in its description the link to its row in the source, so I can go to the detail without searching for it. Ask me: which rows are mine (by client, by region, by type), which time zone rules, and whether there are calendar events you must NOT touch. Run ONE sync with me watching both calendars side by side and show me exactly what you are going to create, change and delete before doing it. Never delete an event that was not created by you. ``` ## What to change before using it - **The do-not-touch rule.** The final line is the important one: a bot with permission to delete on your personal calendar can make a real appointment disappear. - **The time zone.** If you work with clients in another state, define it once or you will publish at the wrong hour. - **The link back.** The original does not have it and it is what makes the calendar usable: see the event and reach the brief in one click. ## Frequently asked questions **Why not sync in both directions?** Because two sources that write to each other end up in conflict and you do not know which one wins. The planning source wins, the calendar reflects it. **Does it work for multiple clients?** Yes, by filtering by client in the initial question. One bot per client is cleaner than one that decides who each row belongs to. **What happens if I delete something in the calendar by hand?** The next run creates it again, because the source wins. If you want to cancel it, cancel it in the source. ## Credit Adapted from [Marketing Calendar Sync](https://botdirectory.ai/bots/marketing-calendar-sync/) by `ericzakariasson`, from the [botdirectory.ai](https://botdirectory.ai) directory (MIT, Copyright 2026 Inbox Zero Inc.). Our version adds the link back to the source row on each event, the rule against deleting events the bot did not create, and the explicit time zone definition: the original synced without those three protections.