PERSONAL PRODUCTIVITY

Guard Outlook focus time against conflicting Google Calendar bookings

When a new event appears on your Google Calendar that overlaps an Outlook deep-work block, it flags the clash and pings you in Microsoft Teams with the conflict details…

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew Google Calendar event createdGoogle CalendarGoogle Calendar
  • ActionRead overlapping Outlook focus blocksOutlook
  • LogicDoes the new event clash with protected time?
  • ActionDraft a side-by-side conflict alertOpenAI
  • OutputSend conflict alert to Microsoft TeamsMicrosoft Teams

What it does

For people living across two calendars, this workflow keeps your Outlook focus blocks safe from events booked on Google Calendar. When a new Google event lands on top of protected Outlook time, it detects the overlap and alerts you in Teams with both events side by side, so you can decide which one wins before the day arrives.

When to use it

When your work calendar is Outlook but colleagues, clients, or personal life book you through Google Calendar, and cross-calendar conflicts silently eat your focus time. Use it to catch double-bookings the moment they happen.

How it works

  1. 1A Google Calendar trigger fires when a new event is created.
  2. 2An Outlook action reads your protected focus blocks in that time range.
  3. 3A logic step checks whether the new Google event overlaps any focus block.
  4. 4If there's a conflict, an OpenAI step writes a concise alert naming both events and the recommended resolution.
  5. 5The alert is delivered to you in Microsoft Teams with the conflict laid out for a quick decision.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  2. 2
    Connect OutlookMail, calendar, contacts.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect Microsoft TeamsChannels, chats, files.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.