PERSONAL PRODUCTIVITY

Real-Time Overbooking Alert on New Calendar Invites

When a new meeting lands on your Outlook calendar, it checks that day's total meeting time and DMs you on Microsoft Teams if accepting would push the day past your overload limit.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew Outlook event createdOutlook
  • ActionRead all events on that dateOutlook
  • LogicSum day's hours vs daily limit
  • LogicPick lowest-priority decline candidate
  • OutputDM overload alert on TeamsMicrosoft Teams

What it does

Acts as a tripwire on every incoming invite. The moment a new event is created on your Outlook calendar, it recalculates that day's meeting total. If the new meeting tips the day over your daily limit (default 6 hours), it sends you a Microsoft Teams direct message naming the offending day, the new total, and which low-priority meeting that day is the best decline candidate.

When to use it

Use it when invites arrive faster than you can mentally track the damage, and you'd rather get nudged at the moment of the invite than discover the overload the night before. Ideal for people who triage meetings reactively but want a guardrail.

How it works

  1. 1An Outlook event-created trigger fires on each new invite.
  2. 2The workflow reads all events on that invite's date from Outlook.
  3. 3A logic step sums the day's meeting hours and checks against the daily limit.
  4. 4If over the limit, it identifies the lowest-priority meeting as a decline candidate.
  5. 5It sends a Teams DM with the day's total and the suggested swap; otherwise it exits silently.

Set it up

What you configure once, before turning it on.

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