Automation: Calendar Conflict Detection and Alert System
For Executive Assistants
Tools: Zapier + Google Calendar (or Outlook) | Time to build: 1 hour | Difficulty: Intermediate Prerequisites: Comfortable with Zapier basics — see Level 4 guide: "Email-to-Task Workflow for Action Item Capture"
What This Builds
A daily automated check that scans your executive's calendar for the next 48 hours and sends you a morning Slack message or email listing: double-bookings, back-to-back meetings with no buffer, meetings missing Zoom links, and travel time not blocked around off-site commitments. You see the issues before your executive does.
Prerequisites
- Zapier account (Starter plan, $20/month)
- Google Calendar or Microsoft Outlook calendar access
- Slack or email for receiving alerts
The Concept
A calendar conflict alert is like a pre-flight checklist for your executive's day. You check it once in the morning; it flags anything that needs fixing before the day starts. The automation handles the checking — you just handle the fixes.
Build It Step by Step
Part 1: Create the scheduled Zapier trigger
- In Zapier, create a new Zap
- Trigger: "Schedule by Zapier" → Every Day → 7:30 AM → Your timezone
- This fires every morning before the workday starts
Part 2: Pull tomorrow's calendar events
- Add a step: "Google Calendar" (or "Microsoft Outlook Calendar")
- Action: "Find Events"
- Set the date range: Today + 1 day (tomorrow's events)
- Set the calendar: Your executive's calendar
What you should see: A list of events from tomorrow's calendar in the test output.
Part 3: Add an AI analysis step
- Add a step: "OpenAI" → "Send Prompt"
- In the Prompt field, write:
You are an Executive Assistant reviewing a calendar for potential issues.
Here are tomorrow's events:
[insert events list from Step 2]
Check for:
1. DOUBLE BOOKING: any two events at the same or overlapping time
2. BACK-TO-BACK: any meetings with less than 10 minutes between them
3. MISSING PREP TIME: any important external meeting without a 15-min prep block before it
4. NO BUFFER FOR TRAVEL: any off-site meeting (look for addresses or "in-person") without travel time blocked
Output:
- If issues found: list each one clearly as a bullet point
- If no issues: "✓ Calendar looks clean for tomorrow"
Keep response short.
Part 4: Send the alert
- Add a final step: "Slack" → "Send Direct Message" (or "Gmail" → "Send Email")
- Message to: yourself
- Message text: "📅 Calendar Check for Tomorrow — [AI output from Step 3]"
- Publish the Zap
Real Example: Complete Workflow
Setup: Zap runs every morning at 7:30am, checks tomorrow's calendar.
Input (from tomorrow's calendar):
- 9:00 AM — Board prep call (Zoom)
- 9:45 AM — Investor meeting (In-person, 123 Main St)
- 9:45 AM — Team standup (Teams)
- 11:00 AM — External partner lunch (Restaurant, 456 Oak Ave)
Output (Slack message at 7:30am):
📅 Calendar Check for Tomorrow:
⚠️ DOUBLE BOOKING: 9:45 AM has two events — Investor meeting and Team standup scheduled at the same time
⚠️ BACK-TO-BACK: Board prep call ends at 9:45 AM, same time as the investor meeting — no buffer for transition
⚠️ NO TRAVEL TIME: Investor meeting is in-person at 123 Main St — no travel time blocked before or after
⚠️ MISSING PREP: External partner lunch at 11 AM — no prep block scheduled
What you do: Fix all 4 issues in 10 minutes — reschedule standup, add travel blocks, add prep time. Your executive never knows they were almost double-booked.
What to Do When It Breaks
- No events appear in Step 2 → Check that the calendar connection is still authorized in Zapier; re-authenticate if needed
- AI misidentifies events → The event data from Zapier may be in a format the AI doesn't parse well; add a Formatter step to clean the data before the AI step
- Too many false alerts → Tighten the AI prompt — specify what counts as "important enough" to flag for prep time
- Zap doesn't fire → Check Zapier Task History; verify the Schedule trigger timezone matches your actual timezone
Variations
- Simpler version: Skip the AI step — just send yourself the raw list of tomorrow's events as a morning digest (no issue detection, but good visibility)
- Extended version: Add a second check at 5pm for the following day, giving you two warning windows for each day
What to Do Next
- Today: Build the simple version (no AI step) — just tomorrow's events delivered every morning
- This week: Add the AI analysis step once you're comfortable with the data flow
- This month: Refine the AI prompt based on which alerts are most and least useful
Advanced guide for Executive Assistant professionals. Tool pricing and interfaces may change.