PERSONAL PRODUCTIVITY

Outlook focus-block defender with auto-reslot of encroaching meetings

Watches your Outlook calendar for meetings that land on top of protected focus blocks, automatically proposes the nearest non-focus slot.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerevent
Steps4
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerOutlook event createdOutlook
  • LogicCheck overlap with protected focus block
  • ActionFind nearest non-focus slot via free/busyOutlook
  • OutputPost Slack swap approval cardSlack

What it does

Focus blocks only work if they survive contact with other people's invites. This workflow treats events you've tagged as focus time as protected, and whenever a meeting is booked over one it computes the nearest open slot that doesn't itself sit on a focus block. It packages the proposed swap — move the meeting, keep the focus block — into a Slack approval so you defend deep-work time without manually fighting every invite.

When to use it

For engineers, writers, and makers who block focus time but watch it get eaten by meetings. Use it when your protected blocks exist on paper but reality keeps overwriting them with calls you didn't ask for.

How it works

  1. 1An Outlook event-created trigger fires when a new meeting is booked.
  2. 2Logic checks whether the new meeting overlaps a focus-tagged block.
  3. 3It exits quietly when there's no encroachment.
  4. 4It searches Outlook free/busy for the nearest slot that avoids all focus blocks.
  5. 5A Slack card proposes moving the meeting with Approve / Keep buttons before the block is lost.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OutlookMail, calendar, contacts.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  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.