PERSONAL PRODUCTIVITY
Outlook travel-time gap guard for back-to-back in-person meetings
Before each day, checks back-to-back Outlook meetings that have physical locations, estimates travel time between them.
How it runs
The automated pipeline, trigger to output.
- TriggerMorning schedule before first meeting
- ActionFetch located Outlook events in orderOutlook
- LogicEstimate travel time vs calendar gap per pair
- ActionCompute trim/shift fix via Outlook free/busyOutlook
- OutputPost Slack travel-conflict alertSlack
What it does
Back-to-back calendar entries look fine on screen but fall apart when one is across town. This workflow looks at tomorrow's Outlook meetings that carry a real-world location, computes the travel time between consecutively scheduled in-person meetings, and finds the cases where the gap is shorter than the commute. For each impossible transition it proposes either trimming the first meeting or pushing the second, and asks you to confirm.
When to use it
For field sales, client-visit roles, executives splitting time across offices, or anyone whose calendar mixes in-person and remote blocks. Use it when 'I'll just be five minutes late' has become a daily pattern caused by impossible commutes baked into the schedule.
How it works
- 1A morning schedule fires before the first meeting.
- 2It reads tomorrow's located Outlook events in time order.
- 3An agent step estimates travel time between each consecutive in-person pair and compares it to the calendar gap.
- 4Branch logic keeps only pairs where commute exceeds the gap.
- 5It computes a fix (trim earlier meeting or shift the later one) using Outlook free/busy.
- 6A Slack message lists each impossible hop with the recommended adjustment.
Set it up
What you configure once, before turning it on.
- 1Connect OutlookMail, calendar, contacts.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Personal Productivity workflows
Log Outlook promises to Airtable with per-recipient commitment rollups
Captures promises from sent Outlook mail into an Airtable base, linking each commitment to a recipient record so you get a running per-contact view of everything you've promised…
Turn Outlook email promises into assigned Asana tasks with due dates
When you send an email containing a commitment, an LLM extracts the promise and its deadline and creates a corresponding Asana task assigned to you with the due date set.
Auto-decline low-priority invites that collide with deep-work blocks
When a new calendar invite lands on top of a protected deep-work block, an AI scores its priority and auto-declines low-value meetings with a polite note proposing alternative…
Decline focus-block meetings and auto-propose a free slot via Notion log
When a low-priority invite hits a focus block, it declines the meeting, finds your next genuinely free slot, replies with a counter-proposal.
Monthly Meeting Cost Report by Email
On the first of each month, tallies every recurring meeting's total person-hours across the team, converts to an estimated dollar cost.
Auto-create weekly focus blocks around existing meetings and guard them
Every Sunday an agent reads next week's confirmed meetings, carves protected deep-work blocks into the open gaps, sets your Slack status to defend them.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.