PERSONAL PRODUCTIVITY

Outlook Transit-Buffer Auto-Blocker for Offsite Meetings

Watches your Outlook calendar for new meetings with a physical address, geocodes the route from your previous event.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew or updated Outlook eventOutlook
  • LogicKeep only events with a physical address
  • ActionFetch the preceding event on the same dayOutlook
  • ActionGet drive time between addresses via routing APIHTTP webhook
  • LogicBranch: existing gap shorter than drive time
  • OutputCreate sized 'Transit' hold in OutlookOutlook

What it does

This workflow eliminates the silent scheduling failure where two in-person meetings get booked back-to-back with no time to physically travel between them. Whenever a new Outlook event lands that has a real-world location, it calculates the travel time from your immediately preceding event and drops a matching 'Transit' block on your calendar so the gap is honored automatically.

When to use it

For field-heavy roles — sales reps, account managers, executives, inspectors — who book client visits across a city and keep arriving late because the calendar treats travel as free. Run it the moment you stop trusting yourself to add buffers by hand.

How it works

  1. 1A new or updated Outlook event fires the trigger.
  2. 2A filter keeps only events that carry a physical street address in the Location field (drops video/phone meetings).
  3. 3The workflow looks back at the event directly before it on the same day and pulls its location.
  4. 4A routing service called over webhook returns the estimated drive time between the two addresses.
  5. 5If the existing gap is smaller than that drive time, a new Outlook 'Transit' event is created to fill the difference.
  6. 6The transit hold is written back to Outlook with the route and ETA in the body.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OutlookMail, calendar, contacts.
  2. 2
    Connect HTTP webhookTrigger any URL on agent actions.
  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.