PERSONAL PRODUCTIVITY

Morning Reschedule Proposer for Focus-Block Conflicts

Each morning it scans today's calendar for meetings sitting on your focus blocks, finds open slots later in the week.

CategoryPersonal Productivity
Enginepaperclip
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily morning schedule
  • ActionPull today's events and free/busy windowsGoogle CalendarGoogle Calendar
  • LogicFind conflicts and propose open alternative slots
  • ActionDraft a tailored reschedule message per organizer
  • OutputEmail reschedule proposals to organizersGmailGmail

What it does

Instead of declining outright, this workflow proposes a better time. Every morning it finds meetings that landed on a protected focus block, searches your free/busy data for the next open slots that respect your working hours, and sends each organizer a polite reschedule proposal by email with one or two concrete alternatives.

When to use it

Use it when you can't just decline meetings — they're real, but they're scheduled badly. Ideal for people who want to defend focus blocks while still being a good collaborator, letting an agent handle the back-and-forth of finding a mutually open time.

How it works

  1. 1A daily morning schedule triggers the run.
  2. 2The flow pulls today's events from Google Calendar and finds those overlapping a focus block.
  3. 3For each conflict, it queries your free/busy availability to find two open slots within your working hours over the next few days.
  4. 4An agent step drafts a tailored, friendly reschedule email per organizer with the proposed slots.
  5. 5The proposals are sent via Gmail, and a summary of what was proposed is logged so you can follow up.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  2. 2
    Connect GmailRead, draft, send, label.
  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.