PERSONAL PRODUCTIVITY

Outlook plus Google cross-calendar overlap reconciler

Merges your Outlook work calendar and Google personal calendar each morning, finds cross-account overlaps that neither calendar can see on its own.

CategoryPersonal Productivity
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMorning schedule before day starts
  • ActionFetch tomorrow's Outlook eventsOutlook
  • ActionFetch tomorrow's Google Calendar eventsGoogle CalendarGoogle Calendar
  • LogicMerge timelines and detect cross-account overlaps
  • OutputSend unified Slack conflict briefingSlack

What it does

People who live in two calendars get blindsided by conflicts that are invisible inside either app — a work meeting in Outlook colliding with a personal commitment in Google. This workflow pulls tomorrow's events from both accounts, builds one combined timeline, and surfaces every overlap that spans the two. For each clash it recommends which side to keep based on rules you set (e.g. external meetings outrank internal holds) and finds an open slot on the movable side.

When to use it

For anyone juggling a corporate Outlook account and a personal Google calendar — consultants, contractors, or employees who keep life and work separate but scheduled. Use it when a recurring personal block keeps getting buried under work invites.

How it works

  1. 1A morning schedule fires before the day begins.
  2. 2It fetches tomorrow's events from Outlook and from Google Calendar.
  3. 3Logic merges both into one timeline and detects cross-account overlaps.
  4. 4It applies your keep/move priority rules and finds an open slot on the side that should move.
  5. 5A single Slack briefing summarizes each conflict and the recommended resolution.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OutlookMail, calendar, contacts.
  2. 2
    Connect Google CalendarEvents, attendees, availability.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.